Scribd
Upload
72 views2 pages

Table of Contents A2

This document outlines the table of contents for a software engineering project. It includes tasks related to requirements analysis, software analysis, design, and quality management. Specifically, it involves identifying stakeholders and requirements, analyzing requirements using structured and object-oriented techniques, addressing requirements through use cases and behavioral specification, and discussing approaches to improve software quality including quality assurance techniques and using a function design paradigm.

Uploaded by

Le Nguyen
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
72 views2 pages

Table of Contents A2

This document outlines the table of contents for a software engineering project. It includes tasks related to requirements analysis, software analysis, design, and quality management. Specifically, it involves identifying stakeholders and requirements, analyzing requirements using structured and object-oriented techniques, addressing requirements through use cases and behavioral specification, and discussing approaches to improve software quality including quality assurance techniques and using a function design paradigm.

Uploaded by

Le Nguyen
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/ 2

TABLE OF CONTENTS

Task 1 – Analysis (1)


P5 Undertake a software investigation to meet a business need.
A. (P5.a) Identify the stakeholders, theirs roles and interests in the case study.
a. Introduction
b. Identify the stakeholders, theirs roles and interests
c. Requirement definition of the project (FRs and NFRs))
d. List out FRs and NFRs in Tune Source project
e. Relationships between the FRs and NFRs.
B. (P5.b) Discuss the technique(s) you did use to obtain the requirements.
a. Introduction
b. 5 requirement gathering techniques
c. Conclusion
M3 Analyse how software requirements can be traced throughout the software lifecycle.
A. Introduction to Requirements Management
B. Traceability
C. Traceability Matrix for Tune Source project
Task 2 – Analysis (2)
P6 Use appropriate software analysis tools/techniques to carry out a software investigation and create
supporting documentation.
Analyse the requirements that you identified in Task 1 using a combination of structural and behavioural
modelling techniques that you have learnt (choose B or C).
A. Introduction
B. Structured analysis and design techniques
a. DFD (1 DFD level 0, 2-3 DFD level 1)
b. ERD (1)
c. Flowchart (2-3)
d. Pseudocode (2-3)
C. Object-Oriented Design techniques
a. Activity diagram (4-5)
b. Class diagram (1)
Task 3 – Design
(P7) Explain how user and software requirements have been addressed.
A. Introduction to Use Case and UC diagram
B. Identifying the Major Use Cases in TS project (1 major UC diagram)
C. Elaborating on the Use Cases (2-3 elaborating UC diagrams)
(M5) Suggest two software behavioural specification methods and illustrate their use with an example.
Discuss how flow chart and pseudocode are used to specify the software behaviour.
A. Program Specification: Syntax, Pseudocode, flowchart
B. Applying the Concepts at Tune Source
(M6) Differentiate between a finite state machine (FSM) and an extended-FSM, providing a application
for both.
Discuss how UML state machine can be used to specify the software behaviour. Differentiate between
FSM And extended FSM using the case study.
A. Finite State Machine (Fsm)
B. Extended Finite State Machine
C. Difference Between Finite And Extended Finite State Machine
(D4) Present justifications of how data driven software can improve the reliability and effectiveness of
software
Discuss how the data-driven approach improves the reliability and effectiveness of software.
A. Definition Of Data Driven Software
B. Data Driven Software For Improvement Of Reliability And Effectiveness Of The Software
C. Improving The Dependability And Effectiveness Of The Software Using Data Driven Software
Task 4 – Software quality management
M4 Discuss two approaches to improving software quality.
(M4.a) Discuss software quality attributes that are applicable to the project.
A. Introduction
B. Software quality attributes
C. Discuss software quality attributes that are applicable to Tune Source
(M4.b) Discuss two quality assurance techniques that can help improve the software quality in the
project.
A. Introduction
B. Quality assurance techniques
C. Conclusion
(D3) Critically evaluate how the use of the function design paradigm in the software development
lifecycle can improve software quality
A. Definition Of Function Desgin Paradigm
B. Use Of Function Design Paradigm In The Software Development Lifecycle To Improve
Software Quality
C. Conclusion

REFERENCES

You might also like