Scribd
Upload
2 views3 pages

Software Analysis and Design (3)

The document outlines key concepts in software analysis and design, including the definition of requirements, the responsibilities of system analysts, and techniques for identifying requirements. It also discusses decision trees, decision tables, data flow diagrams, and the role of data dictionaries in software engineering. These elements are essential for understanding and managing software development processes effectively.

Uploaded by

Ei Moe Lwin Family
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views3 pages

Software Analysis and Design (3)

The document outlines key concepts in software analysis and design, including the definition of requirements, the responsibilities of system analysts, and techniques for identifying requirements. It also discusses decision trees, decision tables, data flow diagrams, and the role of data dictionaries in software engineering. These elements are essential for understanding and managing software development processes effectively.

Uploaded by

Ei Moe Lwin Family
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Software Analysis and Design (3)

5Marks
1. What are Requirements?
 The features that your application must provide
 The descriptions of the services that a system should provide and the
constraints on its operation
 Problem statements or problem description
 A high‐level abstract statement of a service or of a system constraint to a
detailed mathematical functional specification
 Problem statement can validate

2. Responsibilities of System Analysts (OR) Define system analysts (Any 5)


 Analyzing and understanding requirements of intended software
 Understanding how the project will contribute in the organization objectives
 Identify sources of requirement
 Validation of requirement
 Develop and implement requirement management plan
 Documentation of business, technical, process and product requirements
 Coordination with clients to prioritize requirements and remove and ambiguity
 Finalizing acceptance criteria with client and other stakeholders

3. How can be requirements be determined?


 What do we want the system to do? In terms of storing data, any processes,
and the behavior.
 Who are the users of the system?
 What are the needs of the users?
 What does the system need to do to achieve those needs?
 Two basic principles of requirements engineering
1) Separate the problem from the solution
2) Problems and solutions intertwine with one another

4. Number of techniques for identifying requirements


1) Structured workshops;
2) Brainstorming or problem-solving sessions;
3) Interviews; d) Surveys/questionnaires;
4) Observation of work patterns (e.g., time and motion studies);
5) Observation of the system’s organizational and political environment (e.g., socio-
gram);
6) Technical documentation review;
7) Market analysis;
8) Competitive system assessment;
9) Reverse engineering;
10) Simulations;
11) Prototyping;
12) Benchmarking processes and systems
5. Types of Non-functional Requirements

6. Decision Tree
A decision tree gives a graphic view of the processing logic involved in
decision making and the corresponding actions taken. The edges of a decision tree
represent conditions and the leaf nodes represent the actions to be performed
depending on the outcome of testing the conditions.

7. Decision Table
Decision tables specify which variables are to be tested, and based on this
what actions are to be taken depending upon the outcome of the decision making
logic, and the order in which decision making is performed.

8. Structure Analysis and Structure Design (SA/SD) Methodology

9. Data Flow Diagram (DFD)


Hierarchical graphical model of a system that shows the different processing
activities or functions that the system performs and the data interchange among those
functions.
A DFD model only represents the data flow aspects in terms of the input data
to the system, various processing carried out on those data and the output data
generated by the system.
. It does not show
 the sequence of execution of the different functions and
 the conditions based on which a function may or may not be executed.
10. Data Dictionary role in Software Engineering
 A data dictionary provides a standard terminology for all relevant data for use
by the developers working in a project.
 Helps the developers to determine the definition of different data structures in
terms of their component elements while implementing the design.
 The data dictionary helps to perform impact analysis. That is, it is possible to
determine the effect of some data on various processing activities and vice
versa. Such impact analysis is especially useful when one wants to check the
impact of changing an input value type, or a bug in some functionality, etc.

You might also like