180 likes | 416 Views
Asper School of Business University of Manitoba. Systems Analysis & Design. Instructor: Bob Travica. System implementation and deployment. Updated: November 2014. Outline. System implementation System testing Software versioning System deployment Data porting and conversion
E N D
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System implementation and deployment Updated: November 2014
Outline • System implementation • System testing • Software versioning • System deployment • Data porting and conversion • System deployment strategies 3510 Systems Analysis & Design * Bob Travica
Implementation and deploymentactivities 3510 Systems Analysis & Design * Bob Travica
Implementation • Implementation = software development or assembling according to previously created design. • Modularized design (objects and packages; components) – interaction among system components must be implemented using certain standard (SOAP/XML, CORBA, COM) 3510 Systems Analysis & Design * Bob Travica
Testing • Testing = a process of identifying system defects • Develop test cases and test data • A test case specifies starting & ending state, and events to which the software must respond • Test data – data in the defined starting state, which must reach a defined ending state after being exposed to certain event (input). • Modern approach: build to predefined test (Agile Methodology) 3510 Systems Analysis & Design * Bob Travica
Kinds of system tests • Unit testing - individual methods, classes, or components before they are integrated with other software • Defect example: A method for calculating taxes outputs incorrect results. 3510 Systems Analysis & Design * Bob Travica
Kinds of system tests (cont.) • Integration testing - evaluates the behavior of a group of methods or classes (interface compatibility, unexpected parameter values or state interaction, run-time exceptions) • Applied to system or sub-system • Defect example: Results of retrieving a record significantly differ when real database as opposed to dummy database is retrieved 3510 Systems Analysis & Design * Bob Travica
Kinds of system tests (cont.) • Usability testing – software works but fails some of the usability requirements (easy to learn, use & navigate, task efficiency) • Acceptance testing – involves users to determine if system in overall fulfills user requirements 3510 Systems Analysis & Design * Bob Travica
Who Tests Software • Programmers • Unit testing • Testing buddies can test other’s programmer’s code • Quality assurance personnel • Integration and Usability • Users • Acceptance testing • Volunteers for testing beta version of software 3510 Systems Analysis & Design * Bob Travica
Versioning • Alpha version • Test version that is incomplete but ready for some level of testing; dummy data used • Beta version • Test version that is stable enough to be tested by end users for an extended period of time; real data used • Production version • System version that is formally released to users or made operational for long-term use 3510 Systems Analysis & Design * Bob Travica
System deployment • Activities to make a new system operational • Includes: • Installation and configuration • User training • Porting and Converting data • Deployment strategy 3510 Systems Analysis & Design * Bob Travica
Data porting & converting 3510 Systems Analysis & Design * Bob Travica
Direct deployment Parallel deployment Deployment strategy 3510 Systems Analysis & Design * Bob Travica
Phaseddeployment Deployment strategy 3510 Systems Analysis & Design * Bob Travica