CS605 Assignment No. 03

Assignment no. 3 covers Lecture #23 to Lecture #30. Objectives of Assignment: You will learn different concepts relevant to software engineering.  Uploading instructions: Your assignment must be in .doc format.(Any other formats like scan images, PDF, Zip, rar, bmp, docx etc will not be accepted). No assignment will be accepted through email. Rules for Marking: It should be clear that your assignment will not get any credit if: ·         The assignment is submitted after due date. ·         Did not follow the answer sheet guidelines. ·         The submitted assignment does not open or file is corrupted. ·         Your assignment is copied from internet, handouts or from any other student       (Strict disciplinary action will be taken in any of these cases).t  Assignment

Question No 1:  16 Marks You are required to choose a suitable name/terms against each description given in the below table. You are required to write only index numbers (No alphabet) of name/terms in the below table against each description. Note: Solution according to above guidelines will be acceptable only. Name/Terms 1.      Feasibility of the project                             2.      Task Set                                            3.      Adaptation Criteria                           4.      Total Float                                                        5.      Timeline Chart                                  6.      Earned Value Analysis                    7.      Defect Removal Efficiency (DRE)     8.      Error Tracking                                9.      Time Boxing                              10.  SQA Group                                    11.  Walkthroughs                                 12.  Formal Technical Reviews               13.  Quality Control                             14.  Statistical Software Quality Assurance   Note: Answer Sheet on next page (Scroll Down) Name / Terms Descriptions 6 Helps to quantitatively measure the progress and performance of a project as the project team goes through the tasks scheduled for them. 2 To decide which Software process will be most suited for a project with the help of a function having different project characteristics. 1 To assure the progress of the project each task is assigned with a limit and when it is reached the work stops on the current task even if it is still in progress. 5 It provides an optical representation of start and finish dates of a project, what tasks are to be performed, who will perform a specific task, linkage and overlapping between tasks and the duration of each task within a project. 14 It helps the project managers in certain situations to make wise decisions so that the progressing project may not lead to a crisis in terms of schedule and budget at the end of a project. 3 While deciding it we need to be sensible and must utilize our previous experiences along with the results we get through from adaptation criteria and task set selector functions. 11 Firstly, categorize the collected information about defects then try to uncover its root cause and work on to fix what you have traced earlier. 9 A schedule adaptability measure to make sure if a specific task is unable to be completed within the required deadlines should not negatively impact the subsequent tasks and the overall completion date of the project. 7 To check about the required changes and usefulness of the intended software by getting a feedback from different users and customers. 8 To assess the software product’s current state of progress for defects within the design or implementation of the product.

13	To check if the degree of quality of the product is improved while errors are reduced and is Performed before the deployment of the software product.
4	It is decided whether to accept the product without requiring any changes or may completely reject the developed software due to blunders made during its construction.
13	A measure of the ability of the developers to get rid of defects from the software before they are reported by the users after its deployment.
10	A review for quality assurance where the developer/author guides the development team members to go through the project and raise queries about any possible issues, its alternate solutions or standard violations.
8	We use it firstly to recognize the problems in requirements, design and source code etc. and then look for its solution to normalize them.
12	To verify if the intended software is meeting its required requirements or not and to make sure that it is developed according to its specified standards.

·         Write any other alphabet (character) instead of Numeric index number

Downloads link:

https://drive.google.com/file/d/13xiNzHWgl-bDtXaccw5VZ0O4Q-irije-/view?usp=sharing