Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software Engineering (Activities (Requirements (Requirements modeling…

- - - - Process
        
        Elicitation
        
        Information discovery & collection
        
        Interviews & user discussions
        
        Existing documentation
        
        Marketing surveys & user questionaries
        
        Observation
        
        Facilitated meetings
        
        Search for improved methods of existing work
        
        Analysis
        
        Organize requirements
        
        Identify conflicting & ambiguous requirements
        
        Identify relationships between requirements
        
        Ranking requirements priority
        
        System Requirements Specification document
        
        Introduction: purpose, scope, definitions, acronyms, references
        
        Overall description: user requirements, constraints, assumptions
        
        Models: viewpoints
        
        Validations criteria: test cases
        
        References: relevant documentation
        
        Validation
        
        Find potential problems
        
        Formal reviews: review specifications document
        
        Prototyping
        
        Design test cases
        
        Requirements management
        
        Control changes to the requirements
        
        Plan requirements engineering process
      - Roles
        
        Stakeholders
        
        User
        
        Interacts with the system
        
        Customer
        
        Sponsor
        
        Interested in the project
        
        Analyst
        
        Defines "what" not "how"
        
        Defines functional & non-functional requirements
        
        Documents models
        
        Gathers information from stakeholders
        
        Must understand business domain
    - - System's external behavior
      - What system must do and no do
    - - Security
      - Performance
      - Availability
    - - Rules
        
        Simple models
        
        Useful model is a good model
      - Structured analysis
        
        Data model
        
        Consumed & produced objects
        Relationship between these objects
        
        Entity Relationship Diagram (ERD)
        
        Functional model
        
        Transformation applied to data-objects
        
        Process Specification (PSPEC)
        
        Information-flow model
        
        Flow of data-objects through the system
        
        Data Flow Diagram (DFD)
        Multiple levels
        
        Behavioral model
        
        Change of state in response to events
        
        State Transition Diagram (STD)
        
        Control Flow Diagram (CFD)
        
        Control Specification (CSPEC)
      - Object-oriented analysis & design (OOAD)
        
        4+1 View Model
        
        Scenarios
        
        Logical view
        
        Process view
        
        Development view
        
        Deployment view
        
        RUP
        
        Architectural analysis
        
        Use case analysis
        
        Design
        
        Notations
        
        Static
        System parts & their relations
        
        Dynamic (behavioral)
        Interactions of system parts
      - Business process analysis (BPA)
        
        Work-flow applications
        
        Business process management engines
  - - - Control
      - Communication
      - Cost analysis
      - Work breakdown structure
      - Task scheduling
- - - - Tasks inside the activities
      - Flow
      - Artifacts
      - Order & details of the tasks
    - - Waterfall (linear)
        
        Sequential flow
        
        Feedback loops to perform some work before previous activity ends
        
        Changes are difficult to implement
        
        All requirements should be known at the start
    - - Agile
        
        Individuals & interactions
        over processes & tools
        
        Working software
        over comprehensive documentation
        
        Customer collaborations
        over contract negotiation
        
        Respond to change
        over following plan
      - Spiral
        
        Risk-driven
        
        Cyclic incremental growth of system's definition and implementation
        
        Difficult to manage
        
        High cost
      - Rational unified process (RUP)
        
        Phases
        (each mitigates one of risks)
        
        Elaboration
        
        Construction
        
        Transition
        
        Inception
        
        Configurable
        
        Driven by risks
        
        Incremental/iterative delivery
      - Prototyping
        
        Early example, model or release of a product built to test a concept or process
        
        Derive customer requirements
        
        Mitigate technical & architectural risks
      - Incremental delivery
        
        Assign priority to requirements
        
        Define increments
        
        Analyze each increment
        
        Perform activities on increment
      - Iterative development
        Refine the work done
    - - Component-based development
      - Formal methods
      - Aspect-oriented development