in few sentence, say the good thing about the answer of question to this discuss
ID: 3822333 • Letter: I
Question
in few sentence, say the good thing about the answer of question to this discussion and explain how can you improve it.
1.How would you convince your management to allow your project team to incorporate quality reviews into the project life cycle?
Having quality reviews simply an effective method of eliminating problem at earlier stage. It guarantees timely delivery, improve quality, and reduce cost. Have quality reviews ensures project progress prior to testing. And it can also help project team members to educate about the project.
2. What kinds of quality review models (e.g., walkthrough, inspection, other) would you implement?
I would prefer peer review implemented as informal walkthroughs or inspections. Peer reviews are a small team (up to 6 persons) and are members of the project. The peers team composed of personnel from test, quality, and verification and validation. This review process doesn’t include the management of the project. The reviewers are not there to debate engineering judgments or suggest corrections. However, they are responsible in reviewing architecture and requirements, implementation of requirements, tractability, component-level testing, integration, system-level testing, acceptance testing, etc…
3. If you could do a software quality review at only one project life cycle phase, what phase would you pick…and why?
I would say in design phase. That’s where major architectural decisions of how the software will be implementation is made. Also, this is a good place since implementation hasn’t begun and any review feedbacks can be incorporated with relatively minimal effort
4. What software quality metrics would you use to measure software maintainability, how would you use them, and where in the project life cycle would you use them?
I think, there is no easy answer to this question. Maintainability has multiple dimensions…is the code testable?...i.e. easy to test, does it have good test coverage?
Is the code understandable and easy structure, etc..? I would use them mainly in the design and implementation phases.
Explanation / Answer
Answer 1) Well the things mentioned are pretty good. The overall progress of the project is reviewed properly with this thus ensuring the satisafction to the customers as well as the employees. If the project is not tested at various time using different test cases than it may lead to a huge loss to the firm at the last if any fault is found.
Amswer 2) The answer provided seems to be quite impressive as it covers almost all the things but yeah the team also checks for the current progress of the project and if found lagging their job is to boost the team and increase the morale so that they can catch the pace again.
Answer 3) Yes, as it is the intial phase, it would be great to do a software quality review at this phase of the life cycle. With the reviews coming, we can mould the designs according to the needs of the customers as noone of the other phases have started their working. So it won't affect the overall process much.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.