0% found this document useful (0 votes)
24 views

Assignment2 Outline

The document outlines the steps for assignment 2 which includes: 1. Undertaking a software investigation through techniques like interviews and questionnaires to gather requirements for a new digital music platform system. 2. Creating documentation of the software investigation including activity diagrams, use case diagrams, data flow diagrams, and entity relationship diagrams. 3. Designing the database and website for the new system, including wireframes, the database schema, and specific functionality. The assignment will also cover tracing requirements, improving quality, specifying behavior, and differentiating finite state machines from extended finite state machines.

Uploaded by

Tín Phạm
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
24 views

Assignment2 Outline

The document outlines the steps for assignment 2 which includes: 1. Undertaking a software investigation through techniques like interviews and questionnaires to gather requirements for a new digital music platform system. 2. Creating documentation of the software investigation including activity diagrams, use case diagrams, data flow diagrams, and entity relationship diagrams. 3. Designing the database and website for the new system, including wireframes, the database schema, and specific functionality. The assignment will also cover tracing requirements, improving quality, specifying behavior, and differentiating finite state machines from extended finite state machines.

Uploaded by

Tín Phạm
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Outline for assignment 2

Table of contents
List of figures
List of tables
A. INTRODUCTION
B. CONTENT
I. Undertake a software investigation to meet the business need.
1. Techniques used for requirement analysis. Give the reason for the choice
(choose 1 of 3 techniques BPI, BPA, BPR)
2. Techniques used to gather requirements
2.1. Describle software investigation technique (Interview, JAD
Sessions,Questionnaires, Documentation analysis, Observation)
2.2. Choose an appropriate method for Tune Source
2.3. Undertake the investigation
Example: Interview
Step 1: Choose people to be interviewed

Full Name Role Interview Purposes Date Time


Chief Executive Strategic vision for the
Officer new system.
Nguyễn Văn A
Nguyễn Văn B Chief Technology Technologies required
Officer with the new system
Nguyễn Văn C Customers
Nguyễn Văn D Sellers
Nguyễn Văn E IT Staffs
Step 2: Design interview questions

Types of Questions

Closed-Ended Questions Ex: Are you using the Tune Source Digital
Music Platform system

Open-Ended Questions What do you think about the current


system? Has the system met the needs
for the required tasks?
Can you suggest any further improvements
to the system? How do you want the system
to decentralize users? What tasks can these
roles perform in the system?
What are your expectations for system
availability?
What are your expectations for system
performance?
Do you have any requirements on security
and system maintenance?
Does the organization have any
requirements for installation and
configuration of the system?

Probing Questions Let us know your review of the current Tune


Source Digital Platform system.
If there is a change, what would you like to
change?

Step 3: Interview
Step 4: Create interview reports
INTERVIEW REPORT

Interview notes approved by: ____ ________

Person interviewed __ ___________


Interviewer ___ ___________
Date _______________
Primary Purpose:
Summary of Interview:

Participants: Development team, kiosk managers, marketing analyst


and IT department.
JAD:
Content of discussion: Discuss to find out about the feature
+
requirements and divide them: Features that are definitely, possible
and impossible profitable.
+

3. Create software investigation and supporting documentation


3.1. Activity diagram
3.2. Use case diagram (include Use case Description)
3.3. DFD diagram
3.4. ERD diagram
4. Explain how user and software requirements have been addressed (show your
database and your website)
4.1. Using wireframe to design website

4.2. Design database


Convert ERD to Relation Diagram
Show your database diagram
4.3. The specific functionality that the system have includes:
a. login and register
b. Add song
c. Search song
d. Delete, update song

5. Analyse how software requirements can be traced throughout the software lifecycle
(M3)

6. Two approaches to improve software quality (M4)


The quality of software functionality: Using test plan
The quality of software structure: Using flowchart
7. Two software behavioral specification methods and illustrate their use with an
example. (M5)
Đặc tả chính thức
Đặc tả không chính thức
Đặc tả chức năng
Đặc tả mô tả
8. Differentiate between a finite state machine (FSM) and an extended-FSM (M6)

C. Conclusion
D. References

You might also like