Scribd
Upload
16 views2 pages

Software Project Requirements Overview

The document provides instructions for a software engineering project. It states that the Project Requirements Report is due on April 12th 2018 and must be printed and stapled without a cover. Copied work is discouraged and can lead to failing the course. Project presentations will be announced later and no extensions will be given. Failure to present will result in mark deductions. The report must include an abstract, actors, a use case diagram, data flow diagram, 10 fully dressed use cases and remaining use cases in casual format, 3 activity diagrams, and an entity relationship diagram. It must also specify the work done by each group member and figures' authors. The final project report details will be announced later.

Uploaded by

WaqarAhmed
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
16 views2 pages

Software Project Requirements Overview

The document provides instructions for a software engineering project. It states that the Project Requirements Report is due on April 12th 2018 and must be printed and stapled without a cover. Copied work is discouraged and can lead to failing the course. Project presentations will be announced later and no extensions will be given. Failure to present will result in mark deductions. The report must include an abstract, actors, a use case diagram, data flow diagram, 10 fully dressed use cases and remaining use cases in casual format, 3 activity diagrams, and an entity relationship diagram. It must also specify the work done by each group member and figures' authors. The final project report details will be announced later.

Uploaded by

WaqarAhmed
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

Software Engineering

i) Project Requirements Report due on 12th April, 2018


Instructions:
Submit printed hard copies without any covers but properly stapled/clipped
Copied work of any type is strictly discouraged and can lead to ‘F’ grade in whole
course.
Project Presentations will be announced later and no extension shall be awarded.
Your inability to show up for presentation will lead to deduction of marks.

Use Microsoft Visio(2007) for Data Models and Data Flow Diagrams
Use Rational Rose for High Level Use case Diagram

Total Marks: TBD

Project Requirements Report: Marks: 10

Group members+ Project Title

Abstract: One page written description to system’s working, Initial Problems, context,
need of solution

Actors

Use Case Diagram:


High level UCD
DFD
Context Level Diagram

Use Case Description:


Formal (fully dressed)(2 column format for MSSS): 10 use cases (At least 3 use
cases per group member).
Casual Format: all remaining use cases in casual form.
Activity Diagram: 3 activity diagrams for 3 fully dressed use case (1 per group member)

Entity Relationship Diagram:


Identify all entities, their relations, cardinality and modality.

Note:
Work done by each group member
Mention author of figures/use cases
Individual Assessment

Resource Person: Ms. Tayyaba Tariq 1


Project Final Report: will be announced later

Resource Person: Ms. Tayyaba Tariq 2

You might also like