Scribd
Upload
17 views2 pages

Requirement Engineering Delivery Plan

The document outlines a detailed delivery plan for Requirement Engineering, covering various topics such as system analysis, lifecycle models, feasibility analysis, and requirements validation over a series of weeks. It includes in-class tests, group assignments, and self-study components to enhance learning. Key areas of focus include requirements elicitation, analysis strategies, data modeling, and the creation of software requirements documents.

Uploaded by

dreamy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
17 views2 pages

Requirement Engineering Delivery Plan

The document outlines a detailed delivery plan for Requirement Engineering, covering various topics such as system analysis, lifecycle models, feasibility analysis, and requirements validation over a series of weeks. It includes in-class tests, group assignments, and self-study components to enhance learning. Key areas of focus include requirements elicitation, analysis strategies, data modeling, and the creation of software requirements documents.

Uploaded by

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

Requirement Engineering delivery plan

Week Tuesday, Wednesday (SE 1 - Chobodi - 4 hours) Self Study


1. System Analysis Fundamentalss
1

2 2. Introduction to Requirement Engineering

3. Lifecycle Models 3.7. Dynamic Systems Design Methodology (DSDM)


3.1. Systems Development Life Cycle (SDLC)
3.2. Waterfall
3.3. Spiral
3.4. Prototyping
3
3.5. Rapid Application Development
3.6. Agile

4. Information Systems Development In class test


4.1. Project Identification and Initiation
4.2. System Request
4
4.3. Applying the Concepts at Tune Source

5. Feasibility Analysis 5.3. Organizational Feasibility


5.1. Technical Feasibility
5 5.2. Economic Feasibility
5.4. Applying the Concepts at Tune Source

6. Requirements Engineering Processes


6.1. Process Models
6.4. Process improvement.
6 6.2. Actors in requirements engineering processes.
6.3. Process support

7. Requirements Elicitation and Analysis


7.1. Elicitation and analysis processes
7.3. Prototyping.
7 7.2. Elicitation techniques.
7.4. Requirements analysis and negotiation.

8. Requirements Determination
8.1. The Analysis Phase
8.2. Requirements Determination
8.3. The Process of Determining Requirements and 8.6. Joint Application Development (JAD)
Requirements Definition Statement. 8.7. Questionnaires.
8
8.4. Requirements Elicitation Techniques and practice 8.8. Document Analysis, Observation.
8.5. Interviews Release Group Assignment

9. Requirements Analysis Strategies


9.1. Problem Analysis, Root Cause Analysis and
Duration Analysis.
9.2. Activity-Based Costing
9.3. Informal Benchmarking.
9 9.4. Outcome Analysis and Technology Analysis
9.5. Activity Elimination
9.6. Comparing Analysis Strategies.
9.7. Eliciting, Analyzing and Requirements Definition
9.8. System Proposal.
10. Process Modeling
10.1. Data Flow Diagrams to define Business
Processes
10.2. Process Descriptions.
10 10.3. Creating Data Flow Diagrams, Context
DiagramData Flow Diagram Fragments
10.4. Validating Data Flow Diagrams

11. Data Modeling Examples on ERD


11.1. The Entity Relationship Diagram
11.2. The Data Dictionary and Metadata
11.3. Creating an Entity Relationship Diagram
11
11.4. Advanced Syntax
11.5. Validating an ERD.
11.6. Design Guidelines

12. Object oriented design


12.1. OO concepts: classes and objects
12.2. encapsulation, interfaces, inheritance,
polymorphism, message passing, Relating objects
12.3. associations and aggregations
12.4. Static modelling, including UML class
diagrams
12 12.5. Dynamic modelling: including UML interaction Draw UML diagrams for given scenarios
diagrams (e.g. sequence, communication/collaboration
diagrams)
12.6. Use Case Analysis
12.7. Elaborating on the Use Cases (USE CASE
Description).
12.8. Where Clause Logical Operators

13. The software requirements document Create a SRS document


13.1. Types of requirements Viva on Group Assignment
13.2. Non-functional Requirements
13.3. Functional Requirements
13.4. User requirements
13.5. System requirements
13
13.6. Specification: Good practices
13.7. Characteristics of Requirement Statements
13.8. Representing Requirements
13.9. SRS template
13.10. Requirements for critical systems

14. Requirements Validation


14.1. Requirements reviews
14 14.2. Prototyping. 14.4. Requirements testing
14.3. Model validation

15. Requirements Change


15.1. Change Control Process
15.2. Impact Analysis on Changes
15 15.3. Track Requirements Status and issues 15.5. Requirements Management (RM) Tool
15.4. Requirements Traceability Matrix

Revision
Model Paper

You might also like