Business Profile
Most of the organizations follow some suitable sets of steps while any Information system development is conducted. The suitable set of steps are often called as Software Development Life Cycle (SDLC) as most common way to implement any information system. The SDLC life cycle comprises of some sequential stages such as planning, analysis, design, implementation and maintenance (Satzinger, Jackson and Burd 2012). The system development is followed with mentioned stages and sets of activities so that an adaptive methodology can be discussed over the provided case study of Comfort Quilts Limited. SDLC methodology can follow every sequence of activities in the project development; however, the life cycle starts with determining the requirements and analysis of requirements.
The requirement elicitation is a major stage for SDLC along with studying the information system case for Comfort Quilts Limited. Requirement analysis includes project requirement analysis and considered major techniques, items, and stakeholders. The requirement analysis process eliminates repetitive consideration for objectives.
Moreover, in the design phase, the software is designed once, the requirements are analyzed with specifications of output screens. Furthermore, the improvement of software analysis along with different approaches has been developed (Kerzner 2013; Schwalbe 2015). In this report, traditional waterfall approach is discussed with focusing over comparing over some phases of development. The agile approach is considered with self-adaptive process so that individual planning can be applied. The agile approach focuses on object-oriented approach that combines data along with processes so that different advantages and disadvantages could be used for fitting and optimizing over different types of projects.
Traditional waterfall SDLC
SDLC is considered as structured approach along with following the process over top-down processes and all steps that are followed in the same order. The SDLC is systematic way to follow the development process in order to consider the phases and all activities in entire procedures. The activities in each phase consider completion of previous phase before moving into another phase. Milestone could be completed based on the project phases in the timeline specifications (Fleming and Koppelman 2016). The traditional waterfall SDLC procedure considered some signoffs of the stakeholders before the next activities are accomplished. SDLC is often considered to be primarily used process model so that the business process can be appropriately followed with essential sequential way of completion.
Agile methodologies
Agile methodologies focus over people, their activities, and individuals about they work following the schedule. The schedule is followed as waterfall development model activities; the agile considers documentation along with more facets to development model. Traditional model should include accurate and complete requirement specifications along with development. The agile method considers change as unavoidable and the change should be performed during the project development is undertaken (Burke 2013).
Some stakeholders should consider the change management activities in order to filling the working roles to consider successful change management in the project. The individuals are considered for accomplishing the activities over development team so that the activities are segmented under some phases to complete. For this agile methodology, some primary points are considered for certain aspects in completion:
- Individual personnel actions matter
- The documentation should be prepared as per requirements
- Critical need of communication
- Useful modeling tools
- Considering modeling technique for intellect tool-kit
- Upfront design not required
- Reusability can be performed
Business Processes
Agile methodologies focus over people, their activities, and individuals about they work following the schedule. The schedule is followed as waterfall development model activities; the agile considers documentation along with more facets to development model. Traditional model should include accurate and complete requirement specifications along with development (Turner 2016). The agile method considers change as unavoidable and the change should be performed during the project development is undertaken.
Object oriented analysis and design (OOAD)
The object oriented approach considers some stakeholders should consider the change management activities in order to filling the working roles to consider successful change management in the project. The individuals are considered for accomplishing the activities over development team so that the activities are segmented under some phases to complete (Martinelli and Milosevic 2016). Most of the organizations follow some suitable sets of steps while any Information system development is conducted. The suitable set of steps are often called as Software Development Life Cycle (SDLC) as most common way to implement any information system.
The SDLC life cycle comprises of some sequential stages such as planning, analysis, design, implementation and maintenance (Mir and Pinnington 2014). The system development is followed with mentioned stages and sets of activities so that an adaptive methodology can be discussed over the provided case study of Comfort Quilts Limited. SDLC methodology can follow every sequence of activities in the project development; however, the life cycle starts with determining the requirements and analysis of requirements.
Conclusion
The requirement elicitation is a major stage for SDLC along with studying the information system case for Comfort Quilts Limited. Requirement analysis includes project requirement analysis and considered major techniques, items, and stakeholders. The requirement analysis process eliminates repetitive consideration for objectives. Moreover, in the design phase, the software is designed once, the requirements are analyzed with specifications of output screens. Furthermore, the improvement of software analysis along with different approaches has been developed.
In this report, traditional waterfall approach is discussed with focusing over comparing over some phases of development. The agile approach is considered with self-adaptive process so that individual planning can be applied. The agile approach focuses on object-oriented approach that combines data along with processes so that different advantages and disadvantages could be used for fitting and optimizing over different types of projects.
SDLC is considered as structured approach along with following the process over top-down processes and all steps that are followed in the same order. The SDLC is systematic way to follow the development process in order to consider the phases and all activities in entire procedures. The activities in each phase consider completion of previous phase before moving into another phase. Milestone could be completed based on the project phases in the timeline specifications. The traditional waterfall SDLC procedure considered some signoffs of the stakeholders before the next activities are accomplished. SDLC is often considered to be primarily used process model so that the business process can be appropriately followed with essential sequential way of completion.
References
Burke, R., 2013. Project management: planning and control techniques. New Jersey, USA.
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management. Project Management Institute.
Kerzner, H., 2013. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Martinelli, R.J. and Milosevic, D.Z., 2016. Project management toolbox: tools and techniques for the practicing project manager. John Wiley & Sons.
Mir, F.A. and Pinnington, A.H., 2014. Exploring the value of project management: linking project management performance and project success. International journal of project management, 32(2), pp.202-217.
Satzinger, J.W., Jackson, R.B. and Burd, S.D., 2012. Introduction to Systems Analysis and Design: An Agile. Iterative Approach, Course Technology, Cengage Learning.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.
Turner, R., 2016. Gower handbook of project management. Routledge.