ipl-logo

Waterfall Methodology Analysis

1627 Words7 Pages

1.1 Waterfall Methodology The waterfall methodology is referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model, every and each phase must be completed and done before moving to the next phase.Which mean there is no return to the phase after moving to the next one (no iterations) due to that reason, this methodology doesn't fit Elaji project . 1.2 Agile Methodology Agile methodology is a combination of iterative and process that increment . Agile methods represent a relatively new approach to software development, becoming wide-spread in the last decade. agile development solution provides a good fit for mobile application development environment and proposed a new approach …show more content…

This ensures that only features of value to users are developed. RUP provides a well-defined structure for the lifecycle of a project and includes essential milestones where major decisions can be made about the project. RUP project consists of a life cycle . The lifecycle is divided into four phases of development. The phase are as follow: Inception, Elaboration, Construction and Transition . Each phase is organized into a number of iterations .And each of these iterations focus on producing technical deliverables that meet the certain criterion (objectives) of the phase before starting with the next phase. Finally, each phase will be reviewed in details . Elaji project is a mobile application software which requires iterations to add more details and make changes to the design during working without affecting the project .And a cycle in the development methodology is needed to insure that any phase can be reviewed and make changes to it if needed without affecting the project or making any problems. It appears that RUP methodology is the best one to fit the project due to those …show more content…

A business case is built for the project by gaining a good understanding of the project’s requirements and scope and getting to know the project stakeholders. At the end of the Inception Phase the project team will know whether or not to proceed with the project [4] The outcome of the Inception phase is : • A vision document: a general vision of the core project's requirements, key features, and main constraints. • A initial use-case model (10% -20%) complete). • An initial risk assessment. • A project plan, showing phases and iterations. • A business model, if necessary. One or several prototypes . LLD (Low level design document) :a sketch of the GUI is created. [5] So, defining the goals, requirements and scope for the project and specifying all the involved stakeholders and group them if needed is made by collecting important data from target users by asking them questionnaire .After that, an analysis of their answers is made to extract important information from those questionnaire which is an essential step to start the next phase. It involves carrying out detailed study of the target users requirements and arriving at the exact requirements of the proposed system. The target users who have been questioned are

Show More
Related
1395 Words | 6 Pages

This detailed design should be easily converted to programming logic. It is at this stage the technology specifications for implementing the solution, logical structure of the application, design of WebPages, database designs etc are finalized. Test plans and test cases for the application are devised at this stage. Implementation phase – 5 weeks This stage involves implementing the design documentation using the technologies and platforms decided .For

Read More
264 Words | 2 Pages

In that way the job expectations can be clearly explained before a drafting the project details. I would submit the project to the client for final approval and scheduling. I would require the use of software system only to avoid compatibility or version problems. It they must only upgrade do other system requirements I would require the technical and manager use the final approval plan to redesigning a working system in the lab before a live presentation for the client

Read More
865 Words | 4 Pages

1. Planning Before you want to jump right into planning, you want to meet with your client to talk about the project, you want to obtain certain information so that it can help you learn more about the project and whether or not the project should go ahead. Once you accept doing this project, you want to make sure that the client knows the requirements you’re looking for and whether they will meet your standard. For example, your payment estimates for future stages of the project.

Read More
442 Words | 2 Pages

Phase 2 is the logical phase that will map out the entities and attributes required for the tables of the DB using an ER- diagram. Tables are the foundation of your database application”(Caspio Online Help, 2015). Phase 3 is the physical design of the DB this will show tools needed to access the DB, such as how will the users access the DB and the hardware and software needed to make the DB accessible. The relationships among the tables and the structure will be the key to a good design application. When designing a DB one should be conscious of the future use of the DB.

Read More
1198 Words | 5 Pages

Iterative and incremental approach is a better way of developing requirements and modules as well. 4. Requirements provide a complete operating picture of the solution, which helps in taking correct decisions during initial stages of software development life cycle (SDLC). Iterative and Incremental Approach This approach allows us to make changes before it is too late.

Read More
2058 Words | 9 Pages

Unit 312 Design and Produce Documents in a Business Environment 1. Understand the purpose and value of designing and producing high quality and attractive documents. 1.1 Describe different types of documents that may be designed and produced and the different styles that could be used. There are lots of different types of document that can be produced in a business environment, e.g. agendas, minutes, spreadsheets, letters, presentations, business cards, charts etc. Agendas - An agenda is a list of what should happen in a meetings, generally in the in the order in which they are to be taken up.

Read More
1578 Words | 7 Pages

Ronald Reagan You arrive at your next duty station and observe that Airmen are cutting corners to accomplish tasks and morale is the lowest you have ever witnessed. The Airmen look for your leadership to make things better. To be successful in times like these, leaders must exhibit both visionary and ethical leadership. Ronald Reagan personified visionary and ethical leadership during his tenure as the 40th President of the United States. His application of visionary and ethical leadership principles are relevant to me as I seek to develop and to guide future Air Force leaders.

Read More
158 Words | 1 Pages

There are lot's of agile project management throughoutthe world. Here are few of the resources to support the Scrum methodology. Agile Alliance is globally recognized agile community helping agile practice and the principals. Scrum Alliance is a professional organization which helps to promote the usage and understand the Scrum regardless the profit.

Read More
1273 Words | 6 Pages

Tip: Look at Chapter 3 in the Learning resources for more information about audience analysis. Always refer to the Rubric Goals as they identify what the evaluator will be looking for. Main Scenario Setting: Your team at work is implementing a new IT process. This process is based on the implementation of Software Version Control (SVC) for your organization’s development teams.

Read More
1882 Words | 8 Pages

As Williams explains, there are five sequential stages in this method: analyzing requirements, designing the system, development the system, testing the system and deploying it. Each stage of this development model needs to be completed before the next one can begin.

Read More
461 Words | 2 Pages

First, I provide a foundation for my proposal, which will include how the solution works, along with its strengths and weaknesses. Next, I describe why the company needs the solution and identify the issues it will resolve. Then, I calculate the financial benefit of the solution and justify its return on investment. Most importantly, I deliver a cohesive and persuasive message, combining these elements with integrity and

Read More
1048 Words | 5 Pages

It is thus useful to follow spiral model of software development because it involves development of a prototype prior to final implementation of software. Since, the model ensures software upgradation throughout the process cycle so the chances of failure of the software to meet the business need gets minimized (Ahrend, 2013). On the contrary, medium sized organizations have higher amount of resources as compared to startups for software development. In this regard, it can be stated that waterfall framework is suited as it involves repeated tests before the software is finally implemented. Moreover, waterfall model will prevent the final implementation of defective software in the medium scale organizations.

Read More
855 Words | 4 Pages

Number of Interfacing Business Processes and Automated systems. The plan set out for the stakeholder group which engage in complicated and overlying business processes within Griffith University will be different from the stakeholders whose processes are more autonomous or separate. It is common for most Stakeholders not to be involved in the project requirement training but if the training is related to their fields they may be more likely to attend or participate. (BABOK, 2009)

Read More
1150 Words | 5 Pages

Today we know that using an Agile Method is not for every type of project. For projects where change is not so frequent, a traditional model maybe more useful. But where projects are expected to face a lot of change, i.e. scope creep, an Agile Method would be more of an appropriate option. There is nothing we can do to control or stop the requirements from changing. This is why planning and allowing time to make changes for these specific requirements in a project is critical.

Read More
1327 Words | 6 Pages

12. Overreliance on Repeatable Processes Companies may spend years creating an enterprise project management (EPM) methodology. The intent is that the methodology will be used on all projects for all customers and from cradle to grave. Having blind faith in the expectation that repeatable processes will solve problems is a mistake.

Read More

More about Waterfall Methodology Analysis

Related Topics

Open Document