Pleases answer it completely and corectly. Assume you were asked to develop a ti
ID: 670458 • Letter: P
Question
Pleases answer it completely and corectly.
Assume you were asked to develop a ticktacktoe game where two players can play together (on two different machines. Identify the main classes (features) of the game that you need to develop and create a Project plan for this project assuming you have two members in your team. Then create a Gantt chart for the project. What are the Objectives of risk management? What are the technical risks and the human risks for the ticktacktoe game (from Q1) Why is requirement analysis considered to be the most important phase in software development? What are the possible consequences if requirements analysis was done poorly or inadequately? What are the objectives of requirements analysis? What are the deliverables of this phase? What is a structured walk through? What are its objectives? What types of class diagrams are there? What are the objectives of each one? How are they used?Explanation / Answer
2.
The steps involved in risk management are:
Risk identification
Analyzing risk and assessing the damage that it will do
Ranking the risk according to probability of occurrence and impact
Developing a plan to manage the risks with high probability and high impact.
The work product of Risk is management is called as Risk Mitigation, Monitoring and Management Plan (RMMM).
Risk Strategies:- Reactive strategies – very common, also known as fire fighting, project team sets resources aside to deal with problems and does nothing until a risk becomes a problem Proactive strategies - risk management begins long before technical work starts, risks are identified and prioritized by importance, then team builds a plan to avoid risks if they can or minimize them if the risks turn into problems
Project Scheduling:- Activity that distributes estimated efforts across the planned project duration by allocating the effort to specific software engineering tasks. Network of software engineering tasks that will enable the job to get accomplished on time. Done to avoid lateness in project.
3.
The risks are so great that neither the people nor the computers should be trusted or that the system should not be built at all. There are many attributes related to this:
4.
If requirement analysis phase is not completed properly or in a sluggish manner then there might be inconsistencies in the final product.Let’s check out the possible mistakes.
During requirement gathering,Client is not able to provide more details or not sure exactly what is required. Basic reason is, client comes from a non-technical background and not familiar with technical jargons so they find it difficult to share the exact expectations. If requirements are not proper or not completely covered then there is no point of analysis. This will cause a loop of rework in case of development team.
Irregular Communication between the engaged parties. I know from my personal experience that whenever there are more than one parties involved and they don’t interact regularly at the requirement analysis phase, then there is a possibility of disagreement in later phases of development.
Timelines are not achievable. Client is always in a hurry to see the final product so they directly or indirectly plan unrealistic timelines and finally receive a half-baked product.
When the clients receive their final product, by then, expectations changes and they want to introduce more new features which were not part of earlier documents. This behavior can be expected during the project also which pushes the team back on their schedule.
Improper Documentation is another culprit which enhances the possibility of unachievable tasks.
5.
Requirements show the wishes of the customer to the software product (user / customer perspective).
The Requirement Analysis is the most important step in software development.
The main reasons for the success of software projects are:
complete requirements and involved users.
Due to requirements, a common understanding of what a product should be able to do is established. The different approaches of the various project stakeholders (customers, users, developers, etc.) must be taken into account. During the request process, project stakeholders have to agree on one collective point of view and one collective wording.
6.
The main objectives of a structured walkthrough are to ensure that the work presented is:
• accurate
• consistent
• clear
• complete
• optimal
The accuracy of the work presented pertains to how free it is from obvious errors. The consistency of the work presented pertains both to its internal and external consistency to other project work and with respect to project standards and terminology.
The clarity of the work presented pertains to how understandable and unambiguous it is to observers. This is an important factor affecting maintainability. The completeness of the work presented pertains to how well it satisfies the requirements and specifications governing it.