ISOM221+Lecture+20+-+Implementation+I+_Development_

ISOM221+Lecture+20+-+Implementation+I+_Development_ -...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: ISOM221 Information Systems Analysis and Design Lecture 20: Implementation I (Development) 1 Agenda • Be familiar with the system construction process • Understand different types of tests and when use them to use them • Understand how to develop documentation 2 Key Definitions • Construction is the development of all parts of the system: the software itself, documentation, and new operating procedures • Testing helps ensure that the system performs as utlined in the specifications outlined in the specifications • Documentation provides information to make the system easier to use and repair 3 Construction • Programming is the largest, but least risky part of systems development • A program is not considered finished until the st for that program is passed test for that program is passed 4 Project Manager’s Tasks During Programming • Assigning Programming Tasks • Coordinating Activities • Managing the Schedule 5 Assigning Programmers • First, group together related classes, then assign each group to a programmer • Time required is proportional to number of rogrammers programmers – The more programmers, the more coordination, which means less time is spent actually coding – Best to use a small team of programmers – Divide complex projects into autonomous parts 6 The Programmer Paradox • More is not always better than less! • After the “right” number of people are assigned to a programming task, adding more people slows down rather than speeds up completion of the project • Projects requiring a large team should be broken into a series of independent, smaller parts 7 Coordinating Activities • Weekly project meetings • Create and enforce standards • Divide resources into three areas: – Development – Testing – Production • Implement change control measures, e.g., – Program log helps the analysts understand who has worked on what – Use CASE tools (e.g., Visual Studio) to track the status of programs 8 Managing the Schedule • Time estimates must be revised as construction proceeds – Build a 10% error margin into all schedules • Scope creep occurs when new requirements • Scope creep occurs when new requirements are added to the project after the system design was finalized • Risk assessments can help predict potential risks and evaluate their likelihood and potential impact 9 Avoid Classic Mistakes • Research-oriented development – If you use state-of-the art technology, lengthen planned time • Using “low-cost” personnel – If using a significant number of entry level personnel, lengthen planned time • Lack of code control – Use source code library to keep programmers from changing the same code at the same time • Inadequate testing – Always allocate sufficient time for formal testing 10 TIOBE Programming Community Index for November 2010 11 Agenda • Be familiar with the system construction...
View Full Document

This note was uploaded on 12/22/2010 for the course ISOM ISOM221 taught by Professor Sheunhhee during the Spring '09 term at HKUST.

Page1 / 10

ISOM221+Lecture+20+-+Implementation+I+_Development_ -...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online