Differences from version 6 to 12



@@ -1,5 +1,6 @@

 Also know as ''System Design Life Cycle'' and ''Software Development Life Cycle'', [http://en.wikipedia.org/wiki/System_Development_Life_Cycle|WikiPedia's definition] of SDLC is ''"the process of developing information systems through investigation, analysis, design, implementation and maintenance"''.
 
+We currently have an attempt of a simple SDLC which tries to cover everything, but I believe tied in with ((Package Maintainer Teams)), we could have an SDLC for the core and on a per package basis.
 {maketoc}
 To reiterate the major concept, there are the following phases (some of which overlap during the cycle):
 !Feasibility Study

@@ -7,9 +8,9 @@

 !Analysis and Specifications
 This is to analyse the existing and proposed needs of the end users, detailing them to be used as cornerstones of design and testing. Criteria of a successful implementation should be agreed upon, along with functional requirements. This can be done through process flowcharts and data flow diagrams. Reuse of Third Party code (libraries and/or projects) should be identified if cost-effective (time, money, effort). Systems development goals, costs, and deliverables expectations should be identified and documented.
 !Design, Documentation and Quality Assurance
-Based on the agreed upon specifications, design objectives should already be clearly defined. As the design is finalised, this design information will form the basis for User and Technical documentation. Quality Assurance such as automated testing can be catered for during the design stage. Prototyping and use of mock function stubs allow rapid development of users interfaces and class design, which will form the basis of QA testing suites.
+Based on the agreed upon specifications, design objectives should already be clearly defined. As the design is finalised, this design information will form the basis for User and Technical documentation. Quality Assurance such as automated testing can be catered for during the design stage. Prototyping and use of mock function stubs (see ((StubsAndMockObects))) allow rapid development of users interfaces and class design, which will form the basis of QA testing suites.
 !Development
-Apart from coding, items such as policies for Change Control and Third Party Library and Code dependencies should be considered. Several iterations of program and testing should be planned and milestoned tentatively. Testing duties should segregated from development tasks as much as possible to ensure fair analysis. User interfaces, test data for objectives testing and initial systems documentation should be produced now.
+Apart from coding, items such as policies for Change Control and Third Party Library and Code dependencies should be considered. Several iterations of program and testing should be planned and milestoned tentatively. Testing duties should be segregated from development tasks as much as possible to ensure fair analysis. User interfaces, test data for objectives testing and initial systems documentation should be produced now.
 !Systems Implementation
 Implementation and production deployment is planned here (not applicable to our project). File conversion, migration and upgrade paths should all be catered for here, using pilot, parallel or full-system cutovers. User and operations manuals should be complete.
 !Systems Maintenance
Page History
Date/CommentUserIPVersion
09 Jul 2005 (03:55 UTC)
Stephan Borg218.214.1.11312
Current • Source
Stephan Borg218.214.1.1139
View • Compare • Difference • Source
Stephan Borg218.214.1.1138
View • Compare • Difference • Source
Stephan Borg218.214.1.1137
View • Compare • Difference • Source
Stephan Borg218.214.1.1136
View • Compare • Difference • Source
Stephan Borg218.214.1.1135
View • Compare • Difference • Source
Stephan Borg218.214.1.1134
View • Compare • Difference • Source
Stephan Borg218.214.1.1133
View • Compare • Difference • Source
Stephan Borg218.214.1.1132
View • Compare • Difference • Source
Stephan Borg218.214.1.1131
View • Compare • Difference • Source