5.1 SRS Presentation

7/31/2019 5.1 SRS Presentation

1/30

IU CAMPUS MAPNexus Software Development Group


2/30


3/30

Introduction


4/30

Group

Nexus Software Development Group is founded by 4member:

Project manager: Trn Khi Nguyn

Business analyst: Phm Hong Long

Software engineer: Ti Trng Tn Quality assurance engineer: Nguyn Duy Anh


5/30

Project Purpose

IU Campus Map is designed to satisfy the following goals:

Providing the IU campus map

Providing helps to find the rooms location

Providing the guides to the rooms

System overview:

Small scale project

Web Publishing System an IUPortals module


6/30

Project Plan


7/30

Project Schedule


8/30

Project Schedule


9/30

Works Breakdown

Phase Task Description Milestones

Deliverable

Phase 1

T1 Feasibility study FeasibilityReport

T2 Prepare requirement engineeringprocess

T3 Make IUC surveyT4 Requirement elicitation and analysisT5 Feasibility report writingT6 Initial SRS writingT7 SRS writing M1 Complete SRS

Phase 2T8 Architectural designT9 Decomposition

T10 Initial SDS writingT11 SDS writing Initial SDST12 SDS validation M2 Complete SDST13 Implementation M3 Complete System

Phase 3 T14 Create test caseT15 Write test plan M4 Test PlanT16 Validation


10/30

Project Risks

Risk Probability Effect Plan

Requirements for system

are added or modifiedModerate Serious

The requirement engineering is double

checked and signed

Changes in requirements are accepted only

when the backup time is still remains

Loss of a skillful engineer in

groupVery Low Serious

Increase the load of work of other team

member to keep up with plan while

searching for replacement. A negotiation

about schedule might be required.

Client changes development

timeLow Catastrophic

Core functions are prioritized, so if the

development time is cut, product can still do

some main tasks.Development hardware

malfunctionsVery Low Tolerable

Develop and store project in many different

workstation.

Size underestimation/client

change scope of productLow Serious

Double check the schedule and project

scope, sign off before beginning

development


11/30

Product Risks

Risk Probability Effect Plan

Client changes version of Dot

Net Nuke Portal of serverLow Catastrophic

Focus on the portability of system to

prevent incompatibility

Client changes technology

and configuration of serverLow Insignificant

Focus on the portability of system to

prevent incompatibility

Client reduces the budget for

the software project

Moderate Tolerable

Focus on developing core functions.

Other functions are dropped to cope

with budget change


12/30

Information Resources

Area map of National University Area

Map of IU main campus

Map of IU campus in Central Library

Map of IU campus in Natural Science University

Pictures of offices and auditorium

Information of auditorium and functional rooms

Information about requirement of stakeholders.


13/30

Financial Resources

Human resources:

The salary for each team member is 5 million VND/month

Our team consists of 4 members

Project time is 3 months

Total staff salary = 60 million VND

Hardware cost: 8 million VND for hardware maintenance

Software cost: 5 million VND for DotNetNuke GUI package

to satisfy clients request


14/30

Requirements


15/30

Stakeholders

NoStakeholders

Descriptions

1 Students (main user)

Provide functional & nonfunctional requirements2 Teachers (main user)

3 Staffs (main user)

4 Youth Union Provide nonfunctional & domain requirements

5 IU Computer Service CenterGive constraints of the systems performance

Provide non-functional requirements

6 System administrators Manage the database and functions of the system

7 Maintenance group

Maintain system

Back up database

Repair the system


16/30

Functional Requirements

Log in Purpose: In beta testing, only some testing users can use

the system

Input: username & password

Output: the main user interface


17/30


Input username &password

Display theLogin Box

Check username &password

Display User Interface &the area map Lock

account

Display "account islocked"

[ (Valid username - Invalid password) & login attempts < 5 ]

[ Invalid username ]

[ Valid username & password ] [ (Valid username - Invalid password) & login attempt > 5 ]

iMap systemUsers


18/30


View Area Map Purpose: display the location of all 3 IUs buildings in the

National University area

Input: click on the Area Map button

Output: the area map

This function also acts as the reset/home button


19/30


Click on "AreaMap" button

Display theArea Map

iMap systemUsers


20/30


Show room information Purpose: display the rooms information consisting of:

Functionality

Picture

Type of room

etc

Input: the room code

Output: the room information


21/30


Choose a room & click on the"show direction" button

Check theroom code

Search room'sinformation

Display room'sinformation

iMap systemUsers


22/30


Interact with the map Purpose: let users freely interact with the map to explore

the IU campus

This is the main focus of the IU Campus Map system


23/30


Click on abuilding

Click on a button inthe building map

Click on a button inthe floor map

Display theArea Map

Display thebuilding map

[ Click on "Area Map" ]

Display thefloor map

[ Click on a floor ]

Show the roominformation

[ Click on other floor ][ Click on "Area Map" ]

[ Click on a room ]

iMap systemUsers


24/30


Show direction Purpose: show the direction to the required room

Input: the source & destination rooms codes

Output: the source-destination route is highlight


25/30


Click on the highlighted

building

Click on the highlighted floor

Click on the highlighted

room

Choose a room in the menu andpress "Show Location" button

Display the area map with the

destiation building is highlighted

Display the building map with thedestination floor is highlighted

Display the floor map with the

destination room is highlighted

Show roominformation

Perform highlightfucntion

Stop HighlightFunction

iMap systemUsers


26/30

Non-functional Requirements

Environment Technology used: DotnetNuke

Language used: C#

Database used: Microsoft SQL Server 2008

Response Time

Each interaction with the map: less than 20 seconds

Each search attempt: less than 20 seconds

Maps can be rescaled to improve loading time


27/30


Accuracy The rooms location must be accurate

The rooms information and functionality must be up-to-dated

Size

As small as possible

Acceptable size: less than 50 Mb


28/30


Usability Simple and easy to use user interface

The rooms information and functionality must be up-to-dated

Numbers of log in attempts

Acceptable log in attempts: 5


29/30

Domain Requirements

Language Primary language: Vietnamese

Secondary language: English

Symbols and Icons Map symbols should use standard symbols and indicators

Content Mustnt contain any bad information that effects IU

reputation

Mustnt break any IUs regulations


30/30

The EndThank you for your listening

5.1 SRS Presentation

Documents

Transcript of 5.1 SRS Presentation