1. Four laws for software development methodology- • Glass law- (Requirements deficiencies are the prime source of project failure) This law explains the properties which a software development system should have while development of the software. The requirements phase gather the Information which assist in next phase of software engineering (software development). Requirement phase determines all the questions start from W such as after final development where the final product will be use, what type of users use it and what features or services it should provide. It is imperative to continue check and update the requirements up to when the appropriate requirements not finalize. Inadequate, incomplete or irrelative data or information of requirement may generates errors in next development phases of project. The main cause behind erroneous requirement definitions are distinct needs of several users groups and difference among their interest. (santhoshgoud, 2010) For instance- suppose we are developing a software for the senior citizens and by unknowingly or improper requirements definition we put dark colors and small fonts which cause problem for users (old people) to use this end product leads to conflict. • Boehm’s first law- (Errors are most frequent during the requirements and design activities and are the most expensive the later they removed) Generally this law describes that the development of the any proposed project may leads to errors and conflictions. To avoid these errors it is better to check and remove by update the each development phases early than to find and solve a problem later in last phases. In terms of all constraints and factors it is convenient, inexpensive and time saving to fix errors in early stages rather than to search and resolve the errors in the last development phases which results the project development costs high and time consuming. (santhoshgoud, 2010) For example- there is a group of users who orders to develop a project of old age trip system and by mistake or error in requirement phase the age group was noted as a young group trip system, so by using these requirements the final project gone developed and checked then it realize that this project is not same as the user requirement which results to develop the project again from beginning phase which raises the cost as well as time usage. • Boehm’s second law- (Prototyping (significantly) reduces requirement and design errors, especially for user interfaces) This law states that it is better and useful to make prototype of a project or system which is to be develop.
From Ruhling's point of views, the applicable of a requirements contract are both legal and mutually satisfactory, as long as performance is met and buyer's requirements exist, it gives certain protection against price increases, and the possibility of a market predictable.
A work breakdown structure is a key project deliverable that organizes the team 's work into manageable sections. The Project Management Body of Knowledge. defines the work breakdown structure as a "deliverable oriented hierarchical decomposition of the work to be executed by the project team”. Basically the work breakdown structure is something that is put together which defines the scope something that project team can understand. On the other hand, project requirement is kind of a document which tell management, what has to be produced and the exact date of completion. It also is based on responsibility factors. Requirements are the expectations which the product need to fulfill. Requirements are collected from the customer, stakeholders and Sponsor.
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.
Sommerville, I. and Sawyer, P. (2000) Requirements Engineering: A good practice guide. Chichester: Lancaster University.
Focus shall be on utilizing pre-production tools while developing the prototypes. Actual material, wherever possible, shall be used in the development of prototypes rather than having substituted parts. Make the prototypes as closer as possible to actual outputs.
If any of the goals is not achieved then there is flaw in the system and may result in bad outcomes.
Early fixing of errors not only helps save cost but also helps in mitigating the various risks associated with software development and it also helps in improving and monitoring quality of the system etc. It has been proven that the cost to identify and mitigate the errors in the early stages of development of a software will be hundred times less than the cost of removing an error in the software system that has been distributed among hundreds of
Risk management is among the most important practices in the field of project management. A successful project completion and risk management often go side by side. An interesting aspect of project management is that a project can sti...
This can happen when leadership fails to address ongoing issues or does not believe change needs to happen. When organization ions fail to work together as a team due to issue this results in a fail project. Let employees know that you debate issue that can hinder a project. Project Complexity is determined by number of people, number of organizations, number of process linking, and how it can occur gradually. Projects change by their scope, scale, depth and what the project needs to do.
Most of the software development projects change just during the development is in process. This is the reason that agile methodology is best for these projects. There is a room for change in them. Software developers follow these methods and this is the reason that they have further modified these methods according to the different types of projects they confront in their development time.
Sometimes, the stakeholders of the projects have their own personal objectives which become a hindrance in carrying out the project successfully.
The reason of life of a project, however, may be subject to change over time. In three months, for example, there may be a new technology that requires us to adapt the direction that we had planned. In this context, changes are completely valid, substantiated and necessary to ensure that the product/service we are building has value to the customer.
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.
A patient information system called Mental Health Care-Patient Management System (MHC-PMS) is needed to provide medical information about patients with mental health issues and the treatments that are receiving. The MHC-PMS will be a database in which all clinics can interact with to get patient medical information. A Software Requirement Specification (SRS) will be needed which will include four user requirements and four system requirements. A detail description of four nonfunctional and four functional requirements will be found in the SRS. The last part of the SRS will include a detail requirement specification.
To avoid defective design, the design team need not only to fully understand the client’s want but also establish an efficient communication scheme among the designers. Inadequate program scheduling often appears in projects with tight schedules results in some programs getting reduced in order to meet the project timeline is perceived as another risk related to designers. In accurate cost estimate is another risk related to designers/ consultants which often results in deviation of estimated cost from the actual cost. Inadequate site information like soil test results, survey report etc. also can lead to unexpected risk of project delay and cost