7/26/2019 ruq1111.pdf

1/6

Requirement Analysis: The documentation of a project's scope explains

the boundaries of the project, establishes responsibilities for each team member

and sets up procedures for how completed work will be verified and approved.

The documentation may be referred to as a scope statement, statement of work

(SOW) or terms of reference. During the project, this documentation helps the

project team remain focused and on task.

The scope statement also provides the project team leader or facilitator with

guidelines for making decisions aboutchange requests during the project. It is

natural for parts of a large project to change along the way, so the better the

project has been "scoped" at the beginning, the better the project team will beable to manage change. When documenting a project's scope, stakeholders

should be as specific as possible in order to avoidscope creep, a situation in

which one or more parts of a project ends up requiring more work, time or effort

because of poor planning or miscommunication.

Effective scope management requires good communication to ensure that

everyone on the team understands the scope of the project and agrees upon

exactly how the project's goals will be met. As part of project scope management,

the team leader should solicit approvals and sign-offs from the various

stakeholders as the project proceeds, ensuring that the finished project, as

proposed, meets everyone's needs.

Objectives:

Identifying actors.

Identifying use cases.

Modeling context diagram.

Modeling use case diagrams.

Modeling dependency diagram.

http://searchitchannel.techtarget.com/definition/statement-of-work-SOWhttp://searchcio.techtarget.com/definition/change-requesthttp://searchcio.techtarget.com/definition/change-managementhttp://searchcio.techtarget.com/definition/feature-creephttp://searchcio.techtarget.com/definition/feature-creephttp://searchcio.techtarget.com/definition/change-managementhttp://searchcio.techtarget.com/definition/change-requesthttp://searchitchannel.techtarget.com/definition/statement-of-work-SOW

7/26/2019 ruq1111.pdf

2/6

Describing use case narratives.

Describing priority matrix.

Step:1 Requirements use case modeling identify: actors

Term Description

1.Department Department can access all student

attendance, make result sheet for all

student, view course calendar

2.Student Student can access view course and

course calendar.

3.Administration Administrator can edit, update,

delete course calendar, result sheet

and any information

Step 2: Identifying Use Cases (Context Diagram)

7/26/2019 ruq1111.pdf

3/6

Use case Glossary:

Use case name Use case description Participating Actors

and Roles

View course

schedule

this use case describe class

information for teacher

Department

Course information student can see update class

schedule and course calendar.

Student

Update and delete Administrator can update, delete

and confirm any information about

course

Administrator

Step 3:Construct Use-Case Model Diagram(contd.)

7/26/2019 ruq1111.pdf

4/6

Dependency diagram for implementation related use cases:

Fig:Dependency diagram for implementation related usecases.

Step 4:Use-Case narratives

Use Case name University admission information

Use Case ID UC-1

Priority High

7/26/2019 ruq1111.pdf

5/6

Primary Actor Student

Step 4: Use-Case narratives(contd.)

Description This use case describes the steps to universityadmission information through student.

Precondition Student must minimum G.P.A 2.50

Trigger The use case is initiated when the administrator openthe admission pole.

UseCase Ranking and Priority Matrix:

We evaluate use cases on 1-5 scale against six criteria.

1. Significant impact on the architectural design.

2. Easy to implement but contains significant functionality.

3. Includes risky.

4. Time-critical.

7/26/2019 ruq1111.pdf

6/6

5. Complex functions.

6. Cost.

UseCase Ranking and Priority Matrix:

Use case

name

Ranking criteria , 1 to 5

1 2 3 4 5 6

Total

score

Priority Build

cycle

University

admission

information

3 3 3 6 6 6 27 High 1

Admission

related

information

4 4 3 5 5 8 27 High 2

Checking

for

eligibility

2 4 3 5 5 3 22 Medium 3

Select

student

4 3 3 3 5 5 22 Medium 3

Conclusion:

We analyzed the requirements and use case diagrams and use case narratives.

We try to complete our project according to our projections that will fulfill all therequirements.