MindMap Gallery Systems Analyst - Software Requirements Engineering
Software requirements engineering is a key chapter for system analysts, among which requirements elicitation and requirements analysis are chapters where papers frequently appear.
Edited at 2024-04-24 20:26:37Avatar 3 centers on the Sully family, showcasing the internal rift caused by the sacrifice of their eldest son, and their alliance with other tribes on Pandora against the external conflict of the Ashbringers, who adhere to the philosophy of fire and are allied with humans. It explores the grand themes of family, faith, and survival.
This article discusses the Easter eggs and homages in Zootopia 2 that you may have discovered. The main content includes: character and archetype Easter eggs, cinematic universe crossover Easter eggs, animal ecology and behavior references, symbol and metaphor Easter eggs, social satire and brand allusions, and emotional storylines and sequel foreshadowing.
[Zootopia Character Relationship Chart] The idealistic rabbit police officer Judy and the cynical fox conman Nick form a charmingly contrasting duo, rising from street hustlers to become Zootopia police officers!
Avatar 3 centers on the Sully family, showcasing the internal rift caused by the sacrifice of their eldest son, and their alliance with other tribes on Pandora against the external conflict of the Ashbringers, who adhere to the philosophy of fire and are allied with humans. It explores the grand themes of family, faith, and survival.
This article discusses the Easter eggs and homages in Zootopia 2 that you may have discovered. The main content includes: character and archetype Easter eggs, cinematic universe crossover Easter eggs, animal ecology and behavior references, symbol and metaphor Easter eggs, social satire and brand allusions, and emotional storylines and sequel foreshadowing.
[Zootopia Character Relationship Chart] The idealistic rabbit police officer Judy and the cynical fox conman Nick form a charmingly contrasting duo, rising from street hustlers to become Zootopia police officers!
software requirements engineering
Overview
Hierarchy of needs
User needs
Business needs
system requirement
Quality Function Deployment (QFD)
Regular needs
expected demand
unexpected demand
Requirements acquisition
User interviews
Prepare for the interview
Determine the purpose of the interview
Identify users to include in interviews
Prepare questions for interviews
open questions
closed questions
Make arrangements for final interviews
interview process
Limit interview time
Look for exceptions and error situations
Dive into the details
Keep records carefully
Follow-up to the interview
The first task is to absorb, understand, and record the information obtained from the interview
Record the questions that the user cannot answer and arrange them for the next interview for confirmation.
Send an interview memo to the user to confirm the interviewee's contribution and confirm incorrect answers to questions
Advantages and Disadvantages of User Interviews
Good flexibility and wide range of applications
Difficulty coordinating user time
Interviews contain a large amount of information and are difficult to record
Adequate communication skills
Sufficient domain knowledge
Encountering confidential issues and sensitive topics
Interview format
Structured (prepare a series of questions in advance and conduct them in a targeted manner)
Unstructured (only lists rough ideas, all based on on-the-spot performance)
In fact, the most effective is a combination of the two
Questionnaire
Questionnaire production
Identify the problem and type
Writing questions
Design the format of the questionnaire
Advantages and Disadvantages of Questionnaire Surveys
Collect data from large numbers of responses in a short time and at low cost
Anonymous filling is conducive to true answers
Easy to organize and count
Methods to improve questionnaire return rate
Explain the purpose and use of the questionnaire
Explain the answer requirements
Please ask the relevant person in charge to urge you to fill in and return
Participate in customer meetings and answer questionnaires for information processing direction
Reduce questionnaire response time
Set prizes
sampling
Sample size
Calculation formula: heuristic factor (α) * (confidence coefficient/acceptable error) * (confidence coefficient/acceptable error)
Advantages and Disadvantages of Sampling
Speed up data collection
Depends on subjective factors of the system analyst, relying on experience and ability
Storyboard
Storyboard concept
Use tools to explain to users how the system fits the business
Types of storyboards
passive
Similar to pictures and PPT
Active
Similar to movie samples, can be played
interactive
Such as simulation, simulation, prototype
Storyboard creation
Static tools, such as pen and paper, PPT, pictures, etc.
Dynamic tools, such as flash and other animation tools, etc.
Advantages and Disadvantages of Storyboards
The most vivid demand acquisition technology, user-friendly and highly interactive
High time cost and slow acquisition of demand
Joint Requirements Planning (JRP)
Joint Application Development (JAD)
JRP meeting
main principles
Advantages and Disadvantages
It is very effective for ambiguous problems and areas where the needs are least clear.
Meetings are difficult to organize and require high capabilities of relevant personnel
Higher cost, obvious effect
requirements recording technology
task card
Particularly suitable for collecting and organizing information at the business activity level
Scene description
Detailed descriptions of work scenarios and processes by users
user stories
Describe features that are valuable to users
content
Written description (for planning and memos)
Conversation (refining the story)
Test cases (verify story implementation)
User story cards in the form of handwritten
Basic properties
independence
Negotiability
valuable to users
predictability
Short and sweet
Testability
Volere white card
Requirements recording tool similar to task cards
Tool selection
User stories and Volere white cards are positioned as minimum requirements and are suitable for use in agile methods.
Selection principles
Borrow from existing templates
Extend or redefine as needed
Selection should be based on skill factors of team, user, and system analysis
demand analysis
Requirements analysis tasks
definition
Refine, analyze, and carefully review the obtained requirements to ensure that all stakeholders understand and identify them Errors, omissions, deficiencies
Task
Draw system context scope diagram
Create user prototype interface
Analyze feasibility of requirements
Prioritize needs
Model the requirements
Create data dictionary
Use QFD
Needs analysis method
Structured Analysis Method (SA)
ER diagram represents the data model
DFD represents functional model
The main function of DFD
A tool for understanding and expressing user needs and a means of demand analysis
Describing the internal logical process of the system is a tool for expressing the results of demand analysis and the starting point of system design.
The archived text materials are the basis for further revising and enriching the development plan.
Basic symbols of DFD
Data flow, data with a name and flow direction, represented by an arrow with a name
Processing, the transformation of a data stream, represented by a circle
Data storage, accessible stored information, represented by straight line segments
External entities, data sources and data destinations during data processing, are represented by boxes marked with names.
DFD levels
top level image
Describe the input and output data flows and external entities of the entire system
Decompose layer by layer
How to draw DFD
drawing process
Draw system inputs and outputs
Draw DFD interior
Name each data stream
Name the process
Check and revise principles
All DFDs only allow four basic shapes, and each shape must have a name.
Each process has at least one input data stream and output data stream
In DFD, processing numbers need to be assigned by layer.
Any DFD sub-image must be processed correspondingly to the layer above it. The input and output data streams of both must be consistent
In the entire set of DFD, each data storage must have both read and write data streams.
Material flow can be added to the DFD to help users understand the DFD, but control flow cannot be entrained.
STD stands for behavioral model
Best suited for describing event-driven real-time control systems
Represent system behavior by describing system states and events that cause state transitions
The core is the data dictionary
Data dictionary entries
Data element, data item, the smallest unit of data
Data structure, describing the relationship between data elements
data flow
data storage
Processing logic
external entity
The role of data dictionary
List by various requirements
Cross-reference for easy modification
Retrieve name from description content
Consistency check and completeness check
Data dictionary management
Maintained and managed by DBA
Object-oriented analysis (OOA)
Unified Modeling Language UML
UML structure
building blocks
thing
Structural affairs
behavioral matters
group transactions
Comment transaction
relation
rely
association
generalize
accomplish
picture
Class Diagram
object graph
Build diagram
Combined structure diagram
use case diagram
Flowchart
communication diagram
Timing diagram
State diagram
activity diagram
Deployment diagram
Product drawing
Package map
Interactive overview diagram
public mechanism
Specifications (detailed description)
Public classification (general division)
Extension mechanism
Modify
rule
Provisions for putting building blocks together
A view describing the system architecture
logical view
process view
Implementation view
Deployment view
use case view
use case model
Elements of use case diagram
participants
Example
communication association
Identify participants
people
Other systems
Hardware devices, such as IC cards
clock
Merge requirements to obtain use cases
Pay attention to use case naming
Don’t confuse use cases with the steps they contain
Pay attention to distinguishing between business use cases and system use cases
Refine use case descriptions
Use case name
A brief description
event stream
non-functional requirements
Preconditions and postconditions
extension point
priority
Adjust the use case model
inclusion relationship
extended relationship
generalization relationship
Analytical model
Define concept class
Determine the relationship between classes
connection relation
Dependencies
generalization relationship
shared aggregation
combinatorial aggregation
realize relationship
Add responsibilities to a class
Attributes
method
Create interaction diagram
Flowchart
Interactive overview diagram
communication diagram
Timing diagram
Analysis model detail level issues
Model is an auxiliary work in the development process
Problem Domain Oriented Analysis (PDOA)
Emphasize more description and less modeling
Description composition
focus on problem domain
Focus on solving the desired behavior of the system
Analysis process
Gather basic information and develop a problem framework to establish the type of problem domain
Collect further details guided by the question frame type and give a Description of relevant features of the problem domain
Collect and document requirements for the new system
Requirements definition
Requirements definition method
Strictly define methods
Basic assumptions
All requirements can be predefined
Ability to communicate accurately and clearly between developers and users
Use graphics (or text) to fully represent the final system
Suitable for the situation
Only suitable for systems with small scale and simple functions
prototype method
An iterative, cyclical development approach
Issues that need attention
Prototypes can incrementally improve requirements
Prototypes provide a means of overcoming communication difficulties
Prototypes provide a realistic model of the system that users can participate in
Prototypes provide a suitable system development environment
Once requirements are clearly defined through prototyping, system development should be completed using a rigorous approach
software requirements specification
How to write
Write text-based documents with good structure and natural language
Build graphical models
Write formal specifications
content and format
scope
reference materials
need
Eligibility regulations
Requirements traceability
unresolved issues
annotation
appendix
Requirements verification
Requirements review
Technical review type
Review
examine
Walkthrough
Formal review process
plan
Prepare
conduct review
Take action on review results
How to do a good needs review
Hierarchical review
A combination of formal and informal reviews
Staged review
Carefully selected reviewers
Train reviewers
Establish a standard review process
Carry out follow-up work after the review
Be fully prepared for the review
Requirements testing
Concept test cases
The process of requirements testing
Demand management
Requirements change management
demand baseline
demand status
Requirements change
Demand risk management
risky approach
Not enough users participating
User classification ignored
Increasing user demands
Ambiguous needs
unnecessary features
Overly streamlined SSR
inaccurate estimate
Risks related to demand
Requirements tracking
Contents of demand tracking
The purpose of demand tracking
Requirements Tracking Matrix