session 4907

8/8/2019 Session 4907

http://slidepdf.com/reader/full/session-4907 1/29

Session # 49

Software Development

Lifecycle for BusinessPeople

Holly HylandJim McMahon

8/8/2019 Session 4907


2

Goals for Session

Convey basic information aboutthe Software DevelopmentLifecycle (SDLC)

Identify basic processes and abasic vocabulary regarding(SDLC)

Identify sources for additionalinformation.

8/8/2019 Session 4907


3

History of this Session

This session suggestion camefrom IT professionals at lastyears Conference. In the same

way that we offer Financial Aid101 for IT staff, they wanted asession on SDLC for business

people ± to enhance educationand communication.

8/8/2019 Session 4907


4

8/8/2019 Session 4907


5

SDLC Process

Develop Requirements

Determine Architecture

Implement New Code orChanges

Test System Functionality

Deploy New Functionality

8/8/2019 Session 4907


6

Vocabulary - Models

Waterfall (sequential)

±Requirements, design, implement,test, integration, and maintenance

Iterative (cyclical)

±Agile

±Rational Unified Process (RUP)

±Rapid Application Development) (RAD)

8/8/2019 Session 4907


8/8/2019 Session 4907


8

SDLC Examples ± Unified Process

8/8/2019 Session 4907


9

SDLC Examples - Agile

8/8/2019 Session 4907


10

Use Case Example

8/8/2019 Session 4907


11

R equirements

8/8/2019 Session 4907


12

Develop R equirements

Complete

Consistent

Prioritized Structured

Traceable

8/8/2019 Session 4907


13

Determine Architecture

Department of DefenseArchitecture Framework(DODAF) ± standard way to organize an

enterprise architecture into a complimentary andconsistent view.

Zachman Framework ± formal and

highly structured way of defining an enterprise.

Federal Enterprise Architecture ±common methodology for IT within government.

8/8/2019 Session 4907


14

DODAF

8/8/2019 Session 4907


15

Zachman Framework

8/8/2019 Session 4907


16

Federal Enterprise Architecture

8/8/2019 Session 4907


17

Sample System Architecture

8/8/2019 Session 4907


18

Implement New Code or

Changes Computer Programming ± process of

writing code.

Source Code ± sequence of statements ordeclarations written in a programming language.

Programming Language ± artificial

language used to control the behavior of a machine.

±Cobol±Java

8/8/2019 Session 4907


19

Test System Functionality

Testing Traceability Matrix ±mapping the requirements to the test cases.

Test scripts ± scenarios designed to test a

system.

Regression Testing ± ensuring that adding

new functionality did not result in ³breaking´ what workedbefore.

User Acceptance Testing ± the

process of testing with functional users.

Integration Testing ± the process of

testing new functionality

8/8/2019 Session 4907


20

R equirements Flow through to Testing

8/8/2019 Session 4907


8/8/2019 Session 4907


22

User Acceptance Test Cases

Identified in BRD

Test Area Scenario Date

Tested

Notes

AwardClassificationTesting

Test for generation of singlehonours qualification (all possible

classifications according to the

weighting for the award).

Schools to run tests for productionof classifications for all thescenarios they have.

Test for generation of combinedhonours in two disciplines

qualification (all possibleclassifications according to theweighting for the award).


Test for group honoursqualification generation (all

possible classifications accordingto the weighting for the award).

Schools to run tests for productionof classifications for all the

scenarios they have.

Test for Integrated Masters withhonours qualification (all possible

classifications according to theweighting for the award).


8/8/2019 Session 4907


23

Vocabulary ± Supporting

Disciplines Configuration Management ± revision

control.

Documentation ± written text that accompanies

computer software.

Software Quality Assurance ± monitor

software engineering process usually via audits.

Project Management ± discipline of organizing

and managing resources so that projects have a defined scope,quality, time and costs constraints.

User Experience Design ± designing to a

users satisfaction.

8/8/2019 Session 4907


8/8/2019 Session 4907


25

Additional Information

Do a google search on SDLC ±you will find SoftwareDevelopment Lifecycle andSystem Development Lifecycle.Both define process methods.

Visit Wikipedia and search onSDLC

8/8/2019 Session 4907


26

Suggested Questions

Hey<name>, for the 2008-2009AY, do we need to develop oradjust our standard templatesfor requirements gathering sothat we improve our SDLC process?

8/8/2019 Session 4907


27

Suggested Questions

Hey<name>, do we practice awaterfall or iterative process forour SDCL? Or do we use bothprocesses depending on theexpected changes?

8/8/2019 Session 4907


28

Suggested Questions

Hey<name>, I know that you¶regoing to need FAO input for the2008-2009 changes. Can we

get together to develop a projectplan? I want to make sure thatyou have the resources you

need for requirements gatheringand testing.

8/8/2019 Session 4907


29

Contact Information

We appreciate your feedback andcomments. We can be reached at:

Holly Hyland Phone: 202.377.3710

Email: [email protected]

Jim McMahon

Phone: 202.377.3124 Email: [email protected]

session 4907

Documents