This section will focus on analysing different sources of material before a decision is made as to the course of action that this project will take. This will include looking into different development methodologies, Microsoft SharePoint, ways to develop the system, methods for gathering requirements and designing the system, and different testing procedures. 2.1 Development Methodology A software development methodology is a framework used during the development of a system; this framework gives development projects a structure, ensuring that the process remains under control. There are two main methodologies (Software development life cycle methodology and Agile methodology) and a number of models under each of these methodologies. 1. Software Development Life Cycle Methodology a. Waterfall b. V Process c. Spiral d. Incremental i. Incremental Model ii. Evolutionary Delivery e. Prototyping 2. Agile Methodology a. Scrum b. Extreme Programming (XP) Each methodology and model is suited to particular projects, and have their own unique strengths and weaknesses; hence it is important to choose the right one. Software Development life cycle (SDLC) methodology: This is a generic model for software development containing 5 main stages – requirements, design, build, test, and implement as shown by the diagram below [5]. The extent of overlap between stages depends on the model. Agile methodology: Whereas waterfall methodologies are based on phases with checkpoints at each phase, agile methods feature iterations rather than phases. The output of each iteration is working functionality that can be used to respond to changing requirements. This is obtained through collaboration between self-organising and cross-functional teams. S... ... middle of paper ... ...se can happen. For example, when developing the system, it can become apparent that there are particular requirements missing. It would be senseless to refuse to add more requirements just because this stage has already been passed. Incremental models allow the most variation and perhaps suggest the most realistic approach; but it does not mean that you want an incremental approach throughout. At certain times in a software development project, incremental methodologies may be useful; such as towards the end when the more complex functionality is added, or maybe at the beginning to provide stakeholders with functionality to check the system is being developed along the right lines. This demonstrates that it is therefore important to use a combination of these methods whilst completing the system, and not follow a set inflexible format that these models promote.
This model is most effective for developing business software systems because it is easier to change the process to reflect the updated customer requirements. The basic idea behind incremental method is to develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental), thereby allowing software developers to take advantage of what was learned during development of earlier parts or versions of the system. Learning comes from both the development and use of the system, where possible key steps in the process start with a simple implementation of a subset of the software requirements and iteratively enhance the evolving versions until the full system is implemented. At each iteration, design modifications are made and new functional capabilities are
Agile project management is an iterative approach to the planning and monitoring of project processes. Agile projects are conducted in smaller tranches called iterations with each of these iterations closely reviewed and critiqued by the project team (employees, representatives of the clients etc.). The knowledge gained from this process is then used to ascertain the next steps of the
This phase is the main focus of the project managers and stake holders. Meetings with managers, stake holders and users are held in order to determine the requirements like; Who is going to use the system? How will they use the system? What data should be input into the system? What data should be output by the system? These are general questions that get answered during a requirements gathering phase. After requirement gathering these requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be development is also studied.
I recommend Scrum as our methodology because we do not know the requirements, the system needs to be developed quickly, and the system needs to be reliable. Scrum excels at new and changing requirements as well as adapting to new client needs. May Enterprises is currently unsure of what exactly they want so an adaptable methodology would excel. Scrum aims at creating a working system at the end of each sprint. Creating an implementable system quickly and incrementally is one of the main goals of Scrum. Also, because
The book contains the most effective methods of completing a project within its budget, schedule, and the resource constraints. It briefly explains all the stage process of every major project goes through. From creating the plan to monitoring and evaluation, there is a lot for project managers and supervisors to learn.
They are both very powerful tools for team skill building. When team members can identify with the models and learn to move through each stage successfully, it can set organizational standards to new highs. Every business professional should want to keep a copy of these models on his desk because of the growing dependence of teams in organizations. After all, no one wants to be on the losing team. The ineffective team gives no pleasure or feeling of accomplishment to anyone involved!
A software development methodology defines the activities to be undertaken by each individual in the development process, specific techniques for accomplishing those activities, like using a flowchart to document the program logic of a particular software. It also offers guidelines to manage the quality of software at various stages of development.
In every project there are always some universal characteristics that will be shared. They all have a comprehensible and established purpose and very distinct life durations. Overall, all projects are doing something that may possibly be new or yet a one time endeavor but have explicit requirements which include; time, price, and performan...
After the systems planning is complete, the next course of action is the systems analysis phase. This phase includes defining the requirements of the system. This means that the team must conclude what the system needs to do in order to satisfy the users. This is done by forming a requirements...
The Systems Development Life Cycle (SDLC) consists of phases used in developing a piece of software. It is the plan of how to develop and maintain software, and when necessary, replace that software. In 2007 during my hospital’s transition to a new software system, I was fortunate enough to be included in the process. I did not get involved until the implementation phase, but from then on, until now, I remain very active in the process. I decided to highlight the Waterfall Model of SDLC. The Waterfall Model is a “sequential development process” with each phase continuing in a line (McGonigle and Mastrian, 2012, p. 205).
Given the time, it takes to develop large sophisticated software systems it not possible to define the problem and build the solution in a single step. Requirements will often change throughout a projects development, due to architectural constraints, customer’s needs or a greater understanding of the original problem. Iteration allows greater understanding of a project through successive refinements and addresses a projects highest risk items at every stage of its lifecycle. Ideally each iteration ends up with an executable release – this helps reduce a projects risk profile, allows greater customer feedback and help developers stay focused.
In the waterfall method, the steps have to be finished iterative, meaning the next step cannot be started until the previous step is completed. Once the current step is completed, then the next step can be started and so on. The customer does not get a working build during any of the steps and cannot make any changes in the scope at all. Once all steps are completed, the end result is given to the customer and then they can deploy and hope it does what they are needing it to do. If any of the steps need to be changed, then the whole process will need to be restarted from the beginning and the process began again. In agile methods, the process is more flexible. This method is flexible and can allow changes after each iteration. The goal of each iteration is to provide a working build so that the customer can give feedback on it and changes can be made, if needed, so that all requirements are met, or if requirements have changed since the initial build of the
Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change.
The first and most crucial step is to create a solid plan. Plan should include the techniques, tools and data that are going to used in the project. The responsibilities of all the members should be distributed at this step. The utilization of resources and budgeting of the project should be done here. Management tools such as probability and Impact Matrix, FMEA are useful at this point.
In the case of Ferris Healthcare Inc. it was not a big issue as the three models they created were similar. Creating a single methodology for a company is a complex process that must be developed according to the culture of the organization, their project management maturity, and following specific steps: organizing, planning, and managing (Kerzner, 2010. Pages 154-156). For Ferris, it was actually mandatory to develop a single methodology showing guidelines to proceed as they needed an easy to follow procedures to adapt in their new project management implementation, considering their inexperienced executives, line manager, project managers, and line