Information Systems Analysis and Design CSC340 XXIV Other Phases Implementation Phase Testing and Installation Phase Phase Post Installation Tasks Course Summary 2004 John Mylopoulos Other Phases 1 Information Systems Analysis and Design CSC340 The Software Lifecycle Revisited Survey project scope feasibility feasibility study Study current system problem statement Define end user reqs initial requirements project request Select feasible solution detailed requirements Customers delivered system Design new system Maintain improve system new system configuration Select Acquire new S H W design spec Deliver new system S W 2004 John Mylopoulos Construct new system Vendors Other Phases 2 Page Information Systems Analysis and Design CSC340 Software Development Lifecycle Revisited Implementation Phase equipment and software purchases project management controls programming testing and installation Operation Phase training operations control security controls file maintenance and database administration 2004 John Mylopoulos Other Phases 3 Information Systems Analysis and Design CSC340 Implementation Phase Survey Phase Study Phase Global Design Phase Selection Phase Acquisition Phase Detailed Design Phase Implementation Phase Installation of H W and S W site preparation install test Programming plan preparation Building test data test files and DBs Writing and testing programs Installing purchased software Extending adopting purchased software 2004 John Mylopoulos Other Phases 4 Page Information Systems Analysis and Design CSC340 Hardware and Software Purchase Select software DBMS 4GL compilers and loaders project management tools Select hardware needed disks processors workstations monitors networks communications lines network drivers communications devices modems etc How to Purchase establish request for bids or negotiate contract with desired vendor Sources of information to aid in the evaluation Datapro A D Little Seybold reports user groups e g SHARE DECUS news publications e g Computing Canada Computerworld 2004 John Mylopoulos Other Phases 5 Information Systems Analysis and Design CSC340 Installation of System Hardware and Software Site preparation air conditioning installation cable trays cable conduits cable laying installation of satellite relay station power increase installation of clean power ergonomic furniture installation negotiation for new space building false floors all this applies for multi user equipment not for personal machines and or workstations Machine setup system loading and system testing testing software for performance arrangement of furniture training of programming personnel 2004 John Mylopoulos Other Phases 6 Page Information Systems Analysis and Design CSC340 Programming Plan Preparation Review the design specifications Organization of the programmer team chief programmer librarian specialists programmers Team Manager is the person who is in charge of the team and directs the whole implementation Development of detailed construction plan order in which modules will be built and tested specification of naming conventions and parameter passing conventions specification of version numbers of system and development accomplishments specification of control procedures 2004 John Mylopoulos Other Phases 7 Information Systems Analysis and Design CSC340 A Note Chief Programmers In the seventies software teams were defined around chief programmers Chief programmer is the person who conceives and directs the whole implementation Chief programmer team concept has never been validated Some tasks best dealt with by assigning them to one very qualified programmer Other complex tasks done by a team of equal programmers each contributing their specialty Mundane tasks fit best the chief programmer team model 2004 John Mylopoulos Other Phases 8 Page Information Systems Analysis and Design CSC340 Building Test Data Test Files and Databases Have users generate test data if possible Generate full range of data even non key values Generate enough data to test size decisions of programs e g have reports printed on more than one page Generate data that test the full range of potential values e g generate the maximum and minimum input values allowed by a program Note This stage may include the conversion of an existing database 2004 John Mylopoulos Other Phases 9 Information Systems Analysis and Design CSC340 Programming and Testing Here is a top down programming strategy Review program structure Design user interface modules prototyping Test user interface Design top modules Code and test top modules stub testing Design lower modules Code and test lower modules stub testing Stub testing test individual modules by simulating the interfaces to other modules Unit or program testing test all modules that have been coded System testing test the whole system 2004 John Mylopoulos Other Phases 10 Page Information Systems Analysis and Design CSC340 Delivery Phase Implementation Phase Delivery Phase Install files and databases Train end users Convert to the new system Post implementation review Immediate Delayed 2004 John Mylopoulos Other Phases 11 Information Systems Analysis and Design CSC340 System Acceptance Testing Alpha Testing testing on friendly users often in house Beta Testing testing on less friendly users usually an outside group who wants to use the system early End user testing or verification testing test the system in a simulated environment to see whether it meets user specifications and usability requirements often done during alpha testing Validation testing run the system in a live environment testing system performance peak workload performance human engineering test methods and procedures test backup and recovery test audit testing i e is system free of errors 2004 John Mylopoulos Other Phases 12 Page Information Systems Analysis and Design CSC340 Post Implementation Review Involves two subtasks Evaluate operational information system Does it fulfill the objectives set out Does it adequately support transaction processing management reporting Are the projected benefits being realized How do endusers feel about the system Should there be any enhancements When should they be implemented Are the internal controls working adequately Evaluate development processes Did system costs match budgeted amounts Was system completed on time What was the performance of each individual on the project What problems did we encounter What would we do differently 2004 John Mylopoulos
View Full Document
Unlocking...