Lesson PDLC 2010

8/8/2019 Lesson PDLC 2010

1/22

Application Development ToolsIS202

Prof Greg Foster

Room 006, Hamilton [email protected]


2/22

Module Objectives

Implementation phase.

an t e . ramewor .

Fundamental programming concepts.

Using the OO programming approach. Understand the key processes related to building

Appreciate the complexity of applicationdevelopment.


3/22

Module Outcomes

Demonstrate an understanding of:

w ere program eve opmen s n o e OO concepts, characteristics and terminology

the skill required to program in a high-level

development environment

Develop the skills to:

undertake basic program development using C# inthe .NET framework


4/22

Expectations

Attend classes.

Engage with the module.

Self study.

Complete practical exercises honestly

essen a prac ce o re n orce e concep s


5/22

Resources

Text Book:

Be an Parr C# or tu ents, A son Wes ey

Other resources on ADT website as needed.

ADT website for all modulerelated material:

lecture slides practicals

extra material


6/22

Topics of Discussion

System Development Life Cycle

Program Development Life Cycle


7/22

Systems Development Life Cycle


8/22

Implementation Phase

What is the purpose of this phase?

What are the inputs to this phase?

What are the outputs to this phase?

What activities are performed during this

To what extent does the end-user get

involved?


9/22

Purpose

A number of tasks have to be completed

operate.

includes hardware acquisition, softwaredevelopment or acquisition, user preparation,hiring and training of personnel, site and data

preparation, installing, testing, start-up anduser acceptanceStair & Reynolds (2003:577)


10/22

Inputs

Analysis & Design Phases: analysts would have documented the user requirements for the

system during the Analysis Phase. would have documented an overview of the system.

also constructed an Entity Relationship Diagram and ActivityHierarchy Diagram - use these to construct the tables and

relationships if developing the system. OO Approach

UML use case, class, interaction, state, activity

,

needs. if constructing the system, construct the screens/forms and

reports based on the specifications drawn up during the DesignPhase.


11/22

Outputs

Live system

running system that meets the user requirements. should have as few bugs as possible.

Documentation technical

user manual


12/22

Activities

Hardware Acquisition Obtaining the components of the information system.

Software Acquisition or Construction Need to determine if going to purchase.

User Preparation Changing mindsets Getting people to realize new system.

Personnel Decide if new personnel are required Do existing employees needadditional training.

Site and Data Preparation Preparation of the location of the new system, and, ifnecessary, converting manual files into computer files.

Installation Setting up the equipment.

.

Start-up Making the tested system operational.

User Acceptance Handover to client.

Post-Implementation Evaluation Assess the overall quality of the informationsystem.


13/22

End-User Involvement

A strong correlation exists between successful

sys ems an we - ra ne users.

End-User is involved in:

training user documentation

systems test ng post-implementation evaluation


14/22

Program Development Life Cycle


15/22

Analyse Problem

Review program specification package: the programmer reviews the package, which identifies the input,

u u , u .shows relationships among programs.

by thoroughly reviewing these deliverables, the programmerunderstands the nature and requirements of each program.

Meet with analysts and users: enables the programmer to understand the purpose of the programfrom the users perspective.

programmer may wish to recommend a change to some aspect of the. , .

programmer MUST NOT change a requirement without consulting withanalysts and users.

Identify & review programs input, output and processingcomponents.


16/22

Design Programs

Devise a solution algorithm:

Design Tools

Program flowchart graphical representation of relationships

flowcharting software (e.g. Visio) Pseudo code

written representation of program logic

use indentation to depict control structures

Test the solution algorithm

identifying errors in logic is easier at this stage ofthe PDLC than later.


17/22

Code Programs

Translate the solution algorithm into a

. Enter the programming code into the

computer.

Each language has its own syntax.

Should document code as you enter it into thecomputer

use global and internal comments.


18/22

Test Programs

Thorough testing is very important

ec s on ma ng may epen on use o program anits outputs

Users should assist in development of test data.

Looking for bugs/errors (debugging)

syn ax

logic

run-time


19/22

Formalise Solution

Review the program code

look for dead/redundant code & remove it.

Review all the documentation

all documentation should be complete &accurate.


20/22

Maintain Programs

Once implemented, it may be discovered that

e program nee s o e c ange n or er o: correct errors

add enhancements

Starts another iteration of the PDLC!


21/22


22/22

What you need to do next

Textbook Bell & Parr:

read Preface & Chapter 1 practice some of the given examples

try the self-test questions

visit the companion web site:

Read ahead to Chapter 2

Lesson PDLC 2010

Documents

Transcript of Lesson PDLC 2010