Computer engineering 👩‍🎓Important educational notes📚

Solution:- 1.  FTR is useful to uncover error in logic, function and implementation for any representation of the software. 2.  The purpose of FTR is to ensure that software meets specified requirements. 3.  It is also ensure that software is represented according to predefined standards. 4.  It helps to review the uniformity in software development process. 5.  It makes the project more manageable. 6.  Besides the above mentioned objectives, the purpose of FTR is to enable junior engineer to observer the analysis, design, coding and testing approach more closely. 7.  Each FTR is conducted as meeting and is considered successfully only if it is properly planned, controlled and attended. 9.  The purpose of FTR is to verify that the software meets specified requirements. The review meeting: Each review meeting should be held considering the following constraints- Involvement of people: 1.  Between 3, 4 and 5 people should be involve in the revi...

Solution:-  a) Process Metrics These are the metrics pertaining to the Process Quality. They measure efficiency and effectiveness of various processes. b) Project Metrics These are the metrics pertaining to the Project Quality. They measure defects, cost, schedule, productivity and estimation of various project resources and deliverables.found in acceptance)/ total no of testing defects) x 100 THE THREE Ps:- The People • People factor is very much important in the process of software development. • There are following areas for software people like, recruiting, selection performance management, training, compensation, career development, organization and work design, and team/culture development. • Organizations achieve high levels of maturity in the people management area. The Product • Before a project can be planned, product objectives and scope should be established, alternative solutions should be considered and technical and management constraints should be identified. • With...

Solution:- recruitment elicitation Techniques:- 1. Brainstorming 2. Document Analysis 3. Focus Group 4. Interface analysis 5. Interview 6. Observation 7. Prototyping 8. Requirement Workshops 9. Reverse Engineering 10. Survey/Questionnaire 1. Brainstorming Brainstorming is used in requirement gathering to get as many ideas as possible from group of people. Generally used to identify possible solutions to problems, and clarify details of opportunities. 2. Document Analysis Reviewing the documentation of an existing system can help when creating AS–IS process document, as well as driving gap analysis for scoping of migration projects. In an ideal world, we would even be reviewing the requirements that drove creation of the existing system – a starting point for documenting current requirements. Nuggets of information are often buried in existing documents that help us ask questions as part of validating requirement completeness. 3. Focus Group A focus group is a gathering of people who ar...