1 1.0 Introduction- ( Extensions of SRS) 1.1 Purpose 1.2 Scope 1.3 Definition and Acronyms `1.4 References ( extensions of SRS) Table of Contents for the.

1

1.0 Introduction- ( Extensions of SRS)

1.1 Purpose

1.2 Scope

1.3 Definition and Acronyms

` 1.4 References ( extensions of SRS)

Table of Contents for the SDS (Software Development Specifications)

2

2.0 Decomposition Description (part 1)

2.1 Preliminary Design of Architecture

2.2 GUI Components with layouts, navigation

2.3 Database Components – Database Tables, Segments, or Objects

2.4 Data Dictionaryattributes, database components, GUI components


3

2.1 Preliminary Design of Architecture


Client ServerClient Server DB Server DB Server

Environment EnvironmentEnvironment Environment EnvironmentEnvironment

Compaq PCNTVisual Basic …..

Compaq ServerNTVisual BasicMSMQSNA Server (COMTI)

Mainframe IBMXXXMVSCICSCobol Programs

Access IMSCrystalReports SQL - 7

Hand ReadersCamerasVB Screens

TCPIPMSMQ Messages T1/transactions

Twisted Pair

SNA Server(COMTI)TCPIP

CICS TransT1 Line

4

2.2 GUI Components with layouts, navig.


5

2.2 GUI Components with layouts, navig.


Navigation TableState Resulting StateFile Menu

Open OpenDialogueClose Close DialogueNew New SpreadSheet

New SpreadSheetKey FileName …… …….

6

2.0 Decomposition Description (part 1)

2.3 Database Components – Database Table Definitions

Database Table Classes Definitions

Database Definition


7

2.4 Data Dictionaryattributes, database components, GUI components

Entries for every table,

every screen (no in design terms)


8

3.0 Decomposition Description (cont’)

3.1 Component, Module or Item 1 Preliminary Description

Class Diagram at the design level ( iterative)

3.2 Component, Module or Item 2 Prelim Desc

Sequence Diagram (iterative)

3.3 Data Dictionary

with attributes, classes, sequence diagrams


9

3.1 Component, Module or Item 1Preliminary DescriptionClass Diagram at the design level ( iterative)


Cassette

cassetteID: int

cassetteVolumeNo: int

rentMovie()

Party

CID: int

name: StringauthenticateCustomer ()

RentalcassetteID: int

customerID: int

dateRented: daterentMovie()

Movie

movieID: int

movieName: String

orderMovie()

Party View(s)

Movie View(s)

Rental View (s)

Movie Table

Cassette TableRental TableParty Table

Database ClassRent Video

Enroll Customer Return Video

Rent Video View

10

3.2 Component, Module or Item 2 Prelim Desc

Sequence Diagram (iterative)


SystemBorder

Customer selects “process promotionorder” option

Do until no more member orders

Customer enters member number

If member number valid

Get current promtion order header

Do until no more ordered products

Get ordered product information Get product information

Display order

Else

Display error message

Clear Message

Endif

MainWindow

OrderProcesser

OrderProcessing

Window

StartStart orderprocess

Request member number

isMember

Member MemberOrder

reportOrder

MemberOrderedProduct

Product

Validate membernumber

Display order

Display error message

reportProduct

reportOrderedProduct

Clear

New member number

11

4.0 Component Detail Design Document4.1 Component, Module 1,or Item 1 – FOR EACH CLASS

4.1.1 Structure - supertype and sub types of this class 4.1.2 Function –methods of classes with signatures 4.1.3 Interfaces- collaborating classes

4.1.4 Program Interrupts – N/A 4.1.5 Timing and Sequencing N/A 4.1.6 Sequential Control Feature - N/A 4.1.7 Storage Allocation - where class housed (c/s)4.1.8 Application Data – the attributes for each class 4.1.9 Detailed Design Description

Narrative description of each each method.4.2 Component or Module 2 - class 24.3 ……….. 4.n Component or Module n – class 4


12

At this point you would have to replan.

But we will not include this in our SDS.

But you would have needed to schedule the programmers, the database analysts, the database builders, the people who are doing the html if needed the javascript if needed ect.

So I left this in here to make me remember to tell you about the fact that a new plan would need to be done.

But we will not do the plan.

To schedule all the programming staff. While a little project would not be a problem a large one might even hire a different contractor at this point.

13

I. Introduction

Summary of Contents of SDP document

Scope and Purpose of SDP Document

System Level Project Description

System Description


14

Summary of Contents of SDP documentTOC

Scope and Purpose of SDP DocumentThis document will be used to plan project

…. Or get funding….. Or write the RFP

System Level Project DescriptionThis project will…….

System Description

This system will


15

2. Resources and Scheduling

How many people needed?

What type of people?

How long will it take to do this project?

How long will each person be needed?


16

2. Resources and Scheduling

This project will need x# users, y# dp staff

There will be one communications specialist, one data specialist, one unix specialist, one capacity manager, one xxxxx user 4 managers, …..

This project will begin …. And end ….. Person A needed during weeks of etc


17

3. Organization and Staffing

Who are the people needed?

How will the Staffing be organized

How are the users organized?

Who pays? Who knows?


18

3. Organization and Staffing

The organizational chart for the project will be as follows:

Contractor will pay for travel, meeting rooms…...


19

4. WBS (Work BreakDown Schedule)

Week by week, who will be needed

and when?

How much time will be devoted?

How much will this cost?


20

4. Wk1 Wk2 Wk3

Analysis

John 5 hrs 40 hrs 30 hrs

Mary 3 hrs 35 hrs 24 hrs

…...


21

5. Technical Management and Control

How will change management be done?

How will risk be managed?

How will cost be contained?

How will issues be resolved?


22

5. Technical Management and ControlChanges to specification will be done by submitting a change report, approval of change by xyz committee, and scheduling of change.

Risk will be reviewed by the xyz committee each month. Formal risk reports are due to jkl committee quarterly.

Cost reports will be given to mno committee each week for review by xxx manager.

All issues will be reviewed at the project management meeting. Issues which delay development schedules will be resolved by the rst

committee.


23

6. Standards and Procedures

What deliverable standard will be used

What development methodology?

What is the deliverable standard?


24

6. Standards and Procedures

Deliverables will be prepared according to the Summit methodology. All deliverables will be submitted using standard UML. Deliverables will be reviewed by the developers and upon approvals users, management committee, steering committee and final signature by project sponsor.


25

7. Reviews, Audits, and Walkthroughs

How will deliverables be reviewed?

Who will perform auditing?

Who will perform walkthroughs?

What is the approval process?


26

Software Reviews Design Reviews

Design and Coding Checks

Management Reviews

Project Checkpoints concerned with costs, plans, schedules

Quality Reviews

Technical reviews of quality of deliverable products,

standards adherence, documentation

End Product of Reviews

No Action, Refer for Repair, Reconsider overall product


27

Software ReviewsDesign Reviews will be conducted for adherence of good

use of design patterns, and reuse.

Management Reviews

Project Checkpoints will be done weekly for cost control and schedule deadline control.

Quality Reviews

Technical reviews will be conducted at the end of each phase for the quality of deliverable products, standards adherence, and documentation

End Product of Reviews

End of product reviews will be conducted informally on demand.

Table of Contents for the SDP

(Software Development Plan)

28

8. Development Environment

What will be the development hardware/ software. This includes mainframes, PC’s, mini’s, input/output devices, communications devices, database software, operating systems, communications software, and other items of need for development



29

8. Development Environment

The system will be developed using the IBM 3090 mainframe running AIX and Dell Pentium micro computers running windows NT. The development environment will be the same except micros will run windows 95.



30

9. Technical Performance Measurements

How fast will response time be?

How fast will database access be?

How many transactions per sec?

How many terminals on at one time?

What is the MTBF?



31

Performance EvaluationNumber of simultaneous users Number of Connections

Number of Files Size of Tables

Number of Open Files Number of Records

Number of Transactions per interval Response Time

Amount of data processed in a time unit Database Accesses per time unit

Reliability Availability

Backup/Recovery CPU Utilization

Memory Utilization I/O Channel Utilization

Software Utilization Terminals Supported

External Devices Supported



32

9. Technical Performance Measurements

Each transaction will have < 10 sec response time.

Each database will be completed within 10 ms.

The system will process 600 transactions per sec

with 4500 terminals on line.

MTBF will be > 1 hour on the average.



33

10. Documentation

Documentation for technical deliverables, administrative reporting, memos, minutes, meetings, decisions, outstanding issues.



34

10. Documentation

Documentation will be held for all paperwork and decisions. IEEE standard deliverables of the waterfall model will be used for administrative reports. UML will be used to document all technical deliverables. All meetings will be recorded and saved. All decisions will be documented and outstanding issues will be updated every week.



35

11. Verification and Validation

How the system will be verified and validated to assure it is the right system and is developed correctly. The techniques will be spelled out for HOW this system V&V will be conducted.



36

11. Verification and Validation

Deliverables will be verified for conformance with standards using by the QA group. Deliverables will be validated by the xxx user and yyy development committees



37

12. Maintenance

How maintenance will be done.

Who will maintain.

How much time will it take to maintain.



38

12. Maintenance

Approximately 30 hours per month of maintenance is expected approximately one year after turnover. How much maintenance is expected? The system will need 1 Computer Manager, 1 User Manager, and 5 computer programmers assigned. Maintenance environment will be the same as development.



39

13. Human Factors

How many users will be impacted by the new system. How will the educations, training be accomplished. What culture changes are expected.



40

13. Human Factors

There are 3000 users in the group who will need training from computer literacy to usage of the system. A culture change management play will be needed to train the people in the new method of doing business and the computer technology to support this new method.



41

14. Delivery, Installation and Acceptance

What is considered delivered?

How will we install?

What is considered accepted?



42

14. Delivery, Installation and Acceptance

The system will be considered delivered when each of applications is validated by the user group. We will roll out installation by each congressional district. The system will be considered accepted when 4 districts are installed and when one billing cycle has been completed.


1 1.0 Introduction- ( Extensions of SRS) 1.1 Purpose 1.2 Scope 1.3 Definition and Acronyms `1.4 References ( extensions of SRS) Table of Contents for the.

Documents

design termstable of

database analysts

database builders

module n class

design document4

decomposition description

data dictionaryattributes

gui componentsentries