MapleLeaf, LLC SDLC Methodology

MapleLeaf, LLC, has established standard phases and processes in regards to project management methodologies for planning and manage systems development projects. Understanding that no two development efforts are the same, all projects should proceed through the same six phases and are as follows:

System Initiation: This is where the Business Case and Proposed Solution developed during the Project orientation are re-examined to ensure that they are still appropriately defined and correctly address existing organizational strategies and needs. System Initiation: This is where the Business Case and Proposed Solution developed during the Project orientation are re-examined to ensure that they are still appropriately defined and correctly address existing organizational strategies and needs. Systems Requirements Analysis: This is where the business needs are captured with as much detail as possible. Systems Requirements Analysis: This is where the business needs are captured with as much detail as possible. System Design: This builds on the System requirements Analysis and returns results that translate the functional requirements into a complete technical solution. System Design: This builds on the System requirements Analysis and returns results that translate the functional requirements into a complete technical solution. System Construction: This is where the Project Team will build and test the various modules of the application, which includes any and all utilities that are required during the System Acceptance and System Implementation phases. System Construction: This is where the Project Team will build and test the various modules of the application, which includes any and all utilities that are required during the System Acceptance and System Implementation phases. System Acceptance: This is where the team members responsible for developing the application shift the validation efforts to those that will ultimately utilize the system in execution of daily responsibilities. System Acceptance: This is where the team members responsible for developing the application shift the validation efforts to those that will ultimately utilize the system in execution of daily responsibilities. System Implementation: This is the final phase and entails all activities associated with deployment, including, however not limited to, training, installation and transition of ownership from the Project Team to the Performing Organization. System Implementation: This is the final phase and entails all activities associated with deployment, including, however not limited to, training, installation and transition of ownership from the Project Team to the Performing Organization.

MapleLeaf, LLC SDLC Methodology

MapleLeaf, LLC, will primarily employ four SDLC models, although not limited to only these four; they represent the majority of the models that are foreseen as needed at this time. The four models will be utilized depending and the project requirements and available resources and bandwidths. The four models are described as follows, each with graphic description included.

General Model: is the basic model with each phase producing deliverables required by the next phase in the life cycle. The system initiation and requirements analysis are translated in the design. The code is produced in the construction, testing of the code and acceptance by end users to verify the deliverables and then finally implementation.

Waterfall (Linear-Sequential) Model: Advantages: Simple and easy to use Simple and easy to use Easy to manage due to the rigid format, each phase has specific objectives, deliverables and review process Easy to manage due to the rigid format, each phase has specific objectives, deliverables and review process Phases are processed and completed one at a time Phases are processed and completed one at a time Does well with smaller projects where requirements are understood. Does well with smaller projects where requirements are understood. Disadvantages: Adjusting scope during the life cycle can easily terminate the project Adjusting scope during the life cycle can easily terminate the project Working software is not produced until mid life cycle Working software is not produced until mid life cycle High levels of risks and uncertainty High levels of risks and uncertainty Poor model for complex and object-oriented projects Poor model for complex and object-oriented projects Poor model for long and ongoing projects Poor model for long and ongoing projects Poor model when requirements are at a moderate to high risk of changing Poor model when requirements are at a moderate to high risk of changing This will be the most commonly utilized life cycle. Along with its simplicity and ease of understanding, it clearly indicates that each phase is complete in its entirety before the next phase begins. At the conclusion of each phase a review, solution delivery review (SDR) will take place to determine if the project is on the correct path and as to the either continue or discard the project.

V-Shaped Model: Advantages: Simple and easy to use Simple and easy to use Each phase has specific and defined deliverables Each phase has specific and defined deliverables Higher success rate compared to the waterfall method Higher success rate compared to the waterfall method Works well for small projects when requirements are easily understood Works well for small projects when requirements are easily understood Disadvantages: As with the waterfall method, very rigid As with the waterfall method, very rigid Little flexibility allowed, adjusting of scope is difficult and expensive Little flexibility allowed, adjusting of scope is difficult and expensive Software is developed during the implementation phase, not allowing for prototyping Software is developed during the implementation phase, not allowing for prototyping Model does define a clear path for problem resolution determined through testing phases Model does define a clear path for problem resolution determined through testing phases Just as the waterfall model, this is a sequential path of executable processes. Each phase must be completed before the next phase begins. Testing is emphasized more in this model more than in the waterfall method and is developed early prior to any coding being performed and in each phase preceding implementation.

Incremental Model: Advantages: Generates working software quickly and early in life cycle Generates working software quickly and early in life cycle More flexible – less costly to change scope and requirements More flexible – less costly to change scope and requirements Easier to test and debug during smaller iteration Easier to test and debug during smaller iteration Easier to manage risks due to individual risks are identified and handled during its iteration Easier to manage risks due to individual risks are identified and handled during its iteration All iterations are easily managed milestones All iterations are easily managed milestones Disadvantages: Each phase of an iteration is rigid and do not overlap each other Each phase of an iteration is rigid and do not overlap each other Problems may arise pertaining specifically to system architecture if not all the requirements are established at the beginning for the entire software life cycle Problems may arise pertaining specifically to system architecture if not all the requirements are established at the beginning for the entire software life cycle Is an intuitive approach to the waterfall model. Multiple development cycles take place, making this a “multi-waterfall” cycle. Cycles are divided into smaller and more manageable iterations, each passing through the requirement, design, implementation and testing phases.