You are on page 1of 24

Assignments for Software Engineering

Author(s)

VijayKumar Dani, Manjunatha
Prasanna S

Campus Connect
Customization for FP 4.0

Manisha

Authorized by

Pramod Panda

Creation/Revision Date

Sep 2014

Version

4.0

COPYRIGHT NOTICE
© 2014 Infosys Limited, Bangalore, India. All Rights Reserved.
Infosys believes the information in this document is accurate as of its publication date; such
information is subject to change without notice. Infosys acknowledges the proprietary rights of
other companies to the trademarks, product names and such other intellectual property rights
mentioned in this document. Except as expressly permitted, neither this documentation nor
any part of it may be reproduced, stored in a retrieval system, or transmitted in any form or by
any means, electronic, mechanical, printing, photocopying, recording or otherwise, without the
prior permission of Infosys Limited and/ or any named intellectual property rights holders
under this document.
Education, Training and Assessment
Infosys Limited
Electronics City
Hosur Road
Bangalore - 561 229, India.
Tel: 91 80 852 0261-270
Fax: 91 80 852 0362
www.infosys.com
mailto:E&R@infosys.com

0 release CONFIDENTIAL .0 Jun 2014 Manjunatha Prasanna VijayKumar Dani Updated as per educators’ inputs and trainees’ feedback Customization Revision History Version Date Author(s) Reviewer(s) Description 4.0 Jan 2014 VijayKumar Dani Manjunatha Prasanna Initial creation as per FPR 2014 guidelines 2.0 Sep 2014 Manisha Dr.Document Revision History Version Date Author(s) Reviewer(s) Description 1. Kalpana Balaraman Customization for Campus Connect FP 4.. Suresh P.

.................................. 15  Assignment 16: Project Management Phases ................................................................................................... 11  Assignment 12: Performance Testing ............................................................................................................................................................................................................................................................................................................................. 12  Assignment 13: Regression Testing............................................................. 1  Assignment 2: Software Crisis................................................. ii  Customization Revision History ................... 18  Assignment 19: Software Metrics ................................................................................... 19  CONFIDENTIAL ........................................................... 3  Assignment 5: Requirements Elicitation.................................................................... 8  Assignment 10: Software Design Principles ........................................... ii  CONTENTS ................................................................................................................................................................. 8  Assignment 9: Software Design....................................................................................CONTENTS COPYRIGHT NOTICE ......................................................................................................................................................................................................................... 13  Assignment 14: Sanity Testing .................................................... 16  Assignment 18: Defect Classification ................................................... 9  Assignment 11: Integration Testing .......................................................................................................................................................................... 4  Assignment 6: Requirements Classification ....................................................................................................................................... 16  Assignment 17: Quality Control and Quality Assurance ....................................................................................................................... i  Document Revision History................................................................................................................................................................................................................................................................................................................ iii  Assignment 1: Role of Software ......................................................................................................................................................................................................................... 7  Assignment 8: Requirements Verification ....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... 14  Assignment 15: User Experience Design............................................................................................... 6  Assignment 7 : Requirements ................. 1  Assignment 3: Software Development Models ................................................................................... 3  Assignment 4: Requirements Development ......................................

Education Estimated time: 10 minutes Summary of this assignment: In this assignment. As “software houses” emerged.Infosys Limited Assignments for Software Engineering Assignment 1: Role of Software Objective: To identify the role of software in today’s world across a few significant domains Background: Software has made the world a global village today. and many more have exploited software and still there is lot of scope for software to create impact and add value in multiple dimensions. until the sophistication of computer applications outgrew. Education. Software soon took over more and more functions which were hitherto done manually. All organizations. 1. Domains like Health Care. Health Care b. software began to be developed for widespread distribution. Insurance. Software development projects produced Version No: 4. institutions and companies are leveraging the potential of software in automating the critical functions and eliminating laborious manual interventions. The impact of software spans across almost all aspects of human life. Computer programming was an art. This way of doing things was adequate for a while. Airlines c. the focus of development and innovation were on hardware. Insurance e. Airlines. Financial Services.0 Page 1 of 20 . Retail f. Software is also a predominant area for trade and export especially for the countries like India. Programmers did not follow any disciplined or formalized approaches. Assignment 2: Software Crisis Objective: To identify the problem related to software crisis for a given scenario Background: In the early years of computer applications. Retail. Identify the areas (or applications or systems) how software has been leveraged extensively in the following domains a. you have identified the role of software across multiple domains related to day to day life. Banking d. Software was largely viewed as an afterthought. Problem Description: In the context of this background.

identify the most appropriate problem related to software crisis and mention the same in the table provided. It took two hours to fix the defect in the software. i.Infosys Limited Assignments for Software Engineering thousands of source program statements. Time Slippage Cost Slippage Failure at Customer’s Site Untraceable error after delivery Problem Description: In the context of this background. ii. Customer informed the development team about a mal-function in the system. you have mapped the problems related to Software Crisis to the given scenarios. Scenario A: Railway reservation software was delivered to the customer and was installed in one of the metro rail stations at 12:00 AM (mid-night) as per the plan. Version No: 4. The rocket was launched on Sep 15th (delayed by a month). the development team could not identify the defect in the software. The system worked quite fine till the next day 12:00PM (noon). The system crashed at 12:00PM and the railway authorities could not continue using the software for reservation till 02:00PM. As the software was huge and complex. Scenario C: Software for a financial system was delivered to the customer. With the increase in size and complexity of the software. Scenario Situation (A to D given above) A B C D Estimated time: 10 minutes Summary of this assignment: In this assignment. iii. Scenario D: Due to a defect in the software for the baggage handling system. The auto-pilot of the rocket was to be delivered for integration of the rocket on May 15th. there was a loss of $ 2M of revenue for the airport authorities. for each of the scenario mentioned below. Scenario B: A Polar Satellite Launch Vehicle (rocket) was scheduled for the launch on August 15th. following situation resulted which is collectively termed as “Software Crisis”. iv.0 Page 2 of 20 . The design and development of the software for the auto-pilot took more effort because of which the auto-pilot was delivered for integration on June 15th (delayed by a month).

to be analyzed effectively. elicitation.0 Page 3 of 20 . The intention of requirements engineering is to provide a clear definition of requirements of the system. To avoid such issues. TENZ has decided to deploy a robotic arm to pick and place large number of bolts from one tray of a conveyor belt to another tray of a different conveyor belt. specified clearly and verified thoroughly. “TENZ” is a well-established automobile manufacturing plant. TENZ has asked IROBO for demonstrating the robotic arm for the said purpose as a proof of concept. TENZ would like to have a first experience of the robotic arm before signing the MOU (Memorandum of Understanding) with IROBO. interested in automating some of the operations of the plant. Assignment 4: Requirements Development Objective: To identify the various requirements development activities viz. if the customer requirements are not clearly understood. moving one bolt at a time. This phase is a very important phase because. After MOU sign-off. specification and verification for the given scenarios Background: Requirement Engineering produces a specification of what a system should do. analysis. As a first step towards automation. intended to develop robotic systems using IT based solutions. This is the first project being executed by IROBO. Problem Description: Identify the most appropriate SDLC model for this scenario. TENZ would provide the complete set of requirements of the robot. the ambiguity can get into to the other phases of development. Problem Description: Identify the requirement development activities associated with each of the following scenarios Version No: 4. requirements have to be elicited using the right elicitation techniques. you have learnt to identify the software development model for a given scenario. All these activities are collectively termed as requirements development activities. Estimated time: 15 minutes Summary of this assignment: In this assignment.Infosys Limited Assignments for Software Engineering Assignment 3: Software Development Models Objective: To identify the suitable software development model for the given scenario Background: “IROBO” is a new enterprise recently started by a few young entrepreneurs.

Jack identified an incomplete requirement statement 4. Mark is preparing a formal document which includes all of the desired features identified by the survey 3.000. Background: Requirements elicitation is the process of seeking. The techniques used here are important to get stakeholder consensus on the requirements. discovering.Infosys Limited Assignments for Software Engineering 1. The head office is located in London and the bank has presence in more than 20 countries with client base of nearly 500. you have identified the requirement development activities for the given scenarios. Amit a team member is distributing questionnaires to stakeholders for gathering user requirements. Problem Description: KHL is a leading global bank that provides standard banking services to its customers spanning across the globe. 2. Scenario Requirements Development Activity 1 2 3 4 5 6 7 8 Estimated time: 10 minutes Summary of this assignment: In this assignment. Jones is identifying all security related requirements and separating them from the performance related requirements 5. This activity is communication centric and iterative in nature. Assignment 5: Requirements Elicitation Objective: To identify the various requirement elicitation techniques and their usage for a banking case study. 7. Leo a team member is working on requirement development and ensuring that requirements collected should not be vague and unclear. Version No: 4. Joe is creating an online survey questionnaire for requesting user feedback on the desired features of the application to be developed. Lee is conducting a facilitated meeting with the stakeholders to capture the requirements 8. This includes learning and understanding the needs of the users.0 Page 4 of 20 . Merlin a team member is sent to client site to observe the business case and collect typical user requirements 6. acquiring and elaborating requirements.

and other staff for arriving at the requirements for automating transactions Formal and planned requirement discussions in a conference room conducted among managers of diversified branches facilitated by an anchor Survey form circulated amongst the users (account holders) who visit the bank. e-banking facility over internet and phone banking facility over land lines and cellular networks. As part of automation. DD. Task Analysis. ATM interface. the bank has specialized branches for specific customer segments like consumer. Managing Director (MD) of KHL bank has approached FinSoft for the computerization of the bank so that there is no more manual way of doing transactions in any of its branches. Requirements development team in FinSoft has planned for carrying out the requirement elicitation for this project. corporate and the SME’s. Prototyping. KHL Bank aims to be one stop shop for its customers to address their changing financial needs. for the following scenarios identify the most appropriate requirements elicitation techniques (Brainstorming. Currently. to ease their interactions with the bank Analysis for understanding mode of transactions – Checks. Observation. KHL Bank is well known among its clients for world-class processes and speed of execution of transactions as part of core banking. Gold. Workshops. Scenario identification). KHL bank has made a proposal for investing around $200 million in setting-up 24x7 banking support facilities for the customers. etc Ethnographers deployed for understanding the users interaction with bank officials UI design of e-banking portal. KHL bank offers various banking products and services across its customer segments including Core Banking and Wealth Management amongst other services. FinSoft. Questionnaire. Scenarios Requirements elicitation technique Interrogative conversations with Managers. FinSoft is doing such a project for the first time. Version No: 4. In the context of the case study. The bank has decided to leverage IT for automating several of the business processes including:  Managing Accounts  Transaction Management The aim of this proposed banking system is to create a paperless bank there by moving towards e-banking. Cash. a newly established software company has the vision of providing software solutions in the financial sector.0 Page 5 of 20 . Clerks. Cashiers.Infosys Limited Assignments for Software Engineering Tuning with times and ever increasing clients and transactions. MT. the KHL bank users are to be provided with ATM facility.

are those requirements which are not directly concerned with the specific functions delivered by the system.000 calls in a busy hour. you have classified the requirements into functional and non-functional requirements. “Peak transaction volume(s): 20. “Brake System shall sound the alarm for 10 seconds at a frequency of 100Hz when the brake is applied” 4. NFRs are of different types namely usability requirements. as the name suggests. failure to meet a non-functional system requirement may make the whole system unusable. Many non-functional requirements (NFRs) relate to the system as a whole rather than to individual functional requirements.98%” 3. average duration of 20 secs. “Mean time to failure (MTTF): There should be no more than three ‘Severity 1’ outages per month” Estimated time: 10 minutes Summary of this assignment: In this assignment. Version No: 4. you have identified the most appropriate requirement elicitation technique and their usage for a banking case study. Non-functional requirements. 2. 1. portability requirements. thereby satisfying the business requirements. While failure to meet an individual functional requirement may degrade the system. ATM machine shall validate PIN of the user during login along with bio-metric verification.0 Page 6 of 20 . grade of service 99. Problem Description: Classify the following requirements by selecting the appropriate option. reliability requirements etc. deposit. fund transfer etc. Assignment 6: Requirements Classification Objective: To classify the requirements into functional and non-functional requirements Background: Functional requirements (FRs) specify the software functionality that the developers must build into the product to enable users to accomplish their tasks. Estimated time: 15 minutes Summary of this assignment: In this assignment.Infosys Limited Assignments for Software Engineering computer systems Understanding the process involved in each transaction like withdraw.

Infosys Limited Assignments for Software Engineering Assignment 7 : Requirements Objective: Identify the elements in a Software Requirement Specification document. their needs and requirements from the software. Background: The output of requirement analysis phase is the Software Requirements Specification. objectives of the proposed system such that it is proven to be a significant development over the existing system. towards the AS project? System overview Class diagrams Source code Use Cases Flow charts for algorithms realizing the functionality of the system Code review comments Test Results The difference in the scope of the current system to the proposed system Non Functional Requirements Features of new portal to be developed Estimated time: 15 minutes Version No: 4. Problem Description: Article Systems (AS). a giant books franchise has approached IT company ABC Ltd. to help them automate their business processes and shift them online so all of its outlets across the globe would be under one portal. functional and non-functional requirements. decides to follow the waterfall model for development of the project. glossary. business analysis of the client. It should specify what a system should do. AMC Ltd. ABC Ltd. agrees to take on the project and both the companies sit down and strike a deal. Taking into account all the input. the concerned team at ABC designed and developed the SRS. Which of the following are typically expected to be found in the SRS created by ABC Ltd. This discussion covered topics such as the business analysis and operations of AS. After detailed discussion and analysis. the expectations of the client (AS) from ABC Ltd.. A typical SRS usually consists of the System overview (both current and proposed). etc. their current existing system including it's limitations and what the proposed system would do to address these issues.0 Page 7 of 20 .

0. Private attributes Version No: 4. you have identified the requirement defects in the given SRS. It also describes the components at a level of detail that enable their construction. Problem Description: Identify the requirements in the given SRS (CCFP4. Hence it is important that requirements are free from defects like incorrect or conflicting requirements. Background: Software Requirements Specification formally captures the requirements of the software to be developed. Study the class diagram of Easy shop retail application depicted in the “CCFP4. Background: Software Design describes how software is decomposed and organized into components and the interfaces between those components. Class Name b. Problem Description: 1.docx” and identify the following for the class “Customer” a.docx) for following issues:      Incorrect requirements Ambiguous requirements Missing requirements Conflicting requirements Incomplete requirements Estimated time: 15 minutes Summary of this assignment: In this assignment.0-SE EasyShop Manager-Phase1-ClassDiagram.Infosys Limited Assignments for Software Engineering Summary of this assignment: In this assignment. Assignment 9: Software Design Objective: Identify the elements and relationships by analyzing the class diagram of Easy shop retail application case study.SE Premium University Placement Portal SRS (Incomplete). Assignment 8: Requirements Verification Objective: To verify the requirements against the quality attributes. you have identified the elements of an SRS.0 Page 8 of 20 .

Abstraction: Focus on solving a problem by considering the relevant details and ignoring the irrelevant 2. identify the relationship between the elements given below: Class 1 Item RetailOutlet Customer Customer PurchaseBill Tax Class 2 Apparels Item RegularCustomer Address LineItem PurchaseBill Relationship Estimated time: 15 minutes Summary of this assignment: In this assignment. In above document. Private methods e. Encapsulation: Wrapping the internal details. hiding the details of implementation. Assignment 10: Software Design Principles Objective: Identify the design principle that is being violated in relation to the given scenario. Background: A good object oriented design not only meets the specified requirements but also addresses implicit requirements. thereby making these details inaccessible.0 Page 9 of 20 . Coupling & Cohesion: Coupling is the degree to which modules are dependent on each other. 3.Infosys Limited Assignments for Software Engineering c. Public attributes d. Version No: 4. Cohesion is the degree to which a module has a single. independent. A good design is one with loose coupling and strong cohesion. you have identified the elements and relationships among classes. well defined task or responsibility. specifying only the public interface to the clients. Encapsulation separates interface and implementation. Decomposition and Modularization: Dividing the problem into smaller. interactive subtasks for placing different functionalities in different components 4. There are five design principles which address most of the implicit requirements: Software Design Principles: 1. Public Methods 2.

4. Completeness and Primitiveness: Design should ensure the completeness and sufficiency with respect to the given specifications in a very simple way as possible Problem Description: Which of the following design principle(s) have been violated in the following scenarios? 1.0 Page 10 of 20 .Infosys Limited Assignments for Software Engineering 5. Version No: 4. Description 1 Important information of a module is directly accessible by other modules Too many global variables in the program after implementing the design Code breaks in unexpected places Unfulfilled requirements in the code after the design has been implemented Cyclic dependency among classes Huge class doing too many unrelated operations Several un-related functionalities/tasks are carried out by a single module All data of all classes in public Design resulting in spaghetti code An algorithm documented as part of design is not understandable by the programmers 2 3 4 5 6 7 8 9 10 Principal being violated Estimated time: 15 minutes Summary of this assignment: In this assignment. 6. 2. Completeness and Primitiveness All No. Abstraction Decomposition and Modularization Coupling & Cohesion Encapsulation Sufficiency. Sufficiency. 3. 5. you have identified the relevance of design principles.

Similarly in bottom up testing. sub modules and units of TMS are completed. Background: Integration testing is carried out after the completion of unit testing and before the software is delivered for system testing.Infosys Limited Assignments for Software Engineering Assignment 11: Integration Testing Objective: To identify the usage of stubs or drivers in the context of an integration testing scenario. the coding and unit testing of all other modules. Problem Description: Consider the scenario of development of software for Travel Management System (TMS) is in progress. The TMS software has 3 major modules namely Ticket_Booking_Module. Ticket_Validation_Unit and Place_Validation_Unit. Booking_Module and Update_Module. The Ticket_Booking_Module has 3 sub modules namely Enquiry_Module. dummy stubs are required for bottom level modules. dummy drivers are required for top level modules. Except the Ticket_validation_Unit. The top-down Version No: 4.0 Page 11 of 20 . In top down integration testing. Hotel_Booking_Module and Taxi_Booking_Module. identify the usage of stub or driver for the following situations. 1. Travel_Management_System Ticket_Booking_Module Enquiry_Module Hotel_Booking_Module Booking_Module Update_Module View_Module Date_Validation_Unit Source_Validation_Unit Taxi_Booking_Module Place_Validation_Unit Edit_Module Cancel_Module Ticket_Validation_Unit Destination_Validation_Uni In the context of the given scenario. The enquiry module uses Date_Validation_Unit.

Before the tool is deployed. which among the following is necessary?       A Stub for Ticket_Validation_Unit A Driver For Ticket_Validation_Unit A Stub for Enquiry_Module A Driver for Enquiry_Module A Stub For Ticket_Booking_Module A Driver For Ticket_Booking_Module 2. A space craft is expected to function for nearly 8 years in space. The coding and unit testing of all the module. The bottom-up integration is to be started for the TMS software. The different types of performance testing are load testing. Assignment 12: Performance Testing Objective: To identify the different types of performance testing Background: Performance testing tests the non-functional requirements of the system. endurance testing and spike testing. Problem Description: Identify the type of performance testing for the following: 1. you have identified the usage of stubs or drivers in the context of integration testing. Except the Taxi_Booking_Module. Mention any stub or driver needed to carry out the integration testing? 3. Before the launch. sub modules and units of TMS are completed except the Update_Module (coding and testing for Edit_Module. At a time. The top-down integration is to be started for the TMS software. Mention any stub or driver needed to carry out the integration testing? Estimated time: 15 minutes Summary of this assignment: In this assignment. GEC uses an automated tool for conducting objective type test for the trainees. 2. a maximum of 2000 trainees are expected to take the test. stress testing.0 Page 12 of 20 . Global Education Centre (GEC) at Infosys Mysore provides the training for fresh entrants. sub modules and units of TMS are completed. To carry out the integration testing.Infosys Limited Assignments for Software Engineering integration is in progress for the TMS software. Identify the suitable performance testing category to be carried out to ensure that the space craft will be functioning for 8 years in the space as required. The orbit control system of the spacecraft is a real-time embedded system. testing of the tool was carried out to ensure that it is Version No: 4. the coding and unit testing of all other modules. the embedded software is to be tested to ensure that it is capable of working for 8 years in the space. Cancel_Module and View_Module are also completed).

you have identified the different types of performance testing. (ATSL). However. TMS has been developed by Infosys and released to its customer Advance Travel Solutions Ltd. Integration testing. some minor changes are required in the Enquiry Module of the TMS. After analyzing the situation. A university uses its web based portal for publishing the results of the students. regression testing should be done on the system to ensure that the existing features have not been disturbed. Whenever a version is released. Which type of performance testing should have been done during web-site development to avoid this unpleasant situation? Scenarios Scenario 1 Scenario 2 Scenario 3 Scenario 4 Performance Testing Type Estimated time: 15 minutes Summary of this assignment: In this assignment. system testing and acceptance testing were carried out before releasing the final build to the customer. Indicate the performance testing category? 3. Assignment 13: Regression Testing Objective: To identify the usage of regression testing. the maintenance team of that website came to know that it was the consequences of unexpected load on the system which had never happened previously. Problem Description: Consider the scenario of development of software for Travel Management System (TMS) discussed in previous assignment. The customer has approached Infosys with the minor Version No: 4.Infosys Limited Assignments for Software Engineering capable of supporting 2000 simultaneous users. Background: Enhancements are introduction of new features to the software and might be released in different versions. as per the customer feedback during the first month of usage of the software. one of the popular websites crashed as many people logged into the web-site in a short span of time to know the consequences of terrorist attack and for immediate guidelines from the security personnel. the web site crashed.0 Page 13 of 20 . During unexpected terrorist attack. Which type of performance testing should have been done during web-site development to avoid this unpleasant situation? 4. When the results of an examination were announced on the website recently on a pre-planned date.

Which among the following is the testing that the deployment team has preferred to carry out? Select one:    Unit testing Sanity Testing Regression Testing Version No: 4. so regression testing should be carried out Since the acceptance testing is already carried out. integration of the Enquiry Module and quick system testing on Enquiry module should be done The incorporation of minor changes would have introduced new bugs into other modules. has developed a software product for one of its clients. or other analysis. Assignment 14: Sanity Testing Objective: To identify the usage of Sanity Testing Background: Sanity testing is a very brief run-through of the functionality of a computer program. you have identified the relevant type of testing needed. the deployment team prefers to carry out a quick round of testing. The development team of Infosys has incorporated those changes. Problem Description: Dev Software Ltd. to assure that part of the system or methodology works roughly as expected. and delivered the software to testing team to test the upgraded software.Infosys Limited Assignments for Software Engineering changes for upgrading the software. The deployment team has visited customer site to install the software so that the customer could start acceptance testing. system. it is enough if the team performs sanity testing on the Enquire module No need of testing any module Estimated time: 10 minutes Summary of this assignment: In this assignment. Which among the following statement is true?     Since minor changes are there.0 Page 14 of 20 . All the stages of testing have been completed including system testing. calculation. Prior to handover of the product to customer for acceptance testing.

The new phone is nice to use but lacks features as compared to other brands in market. Background: User Experience design (UXD) focuses on designing the overall experience people have. User Experience Facet Estimated time: 10 minutes Summary of this assignment: In this assignment. you have mapped the observations to appropriate user experience facets. 2. 6. however.Infosys Limited  Assignments for Software Engineering Acceptance testing Estimated time: 10 minutes Summary of this assignment: In this assignment. 7. Useful Usable Desirable Findable Accessible Credible Valuable Problem Description: Map the following observations given during user experience design review to one of the facets: Observations I cannot locate the search options in this website. 5. 3. It takes too long to switch among pages of the portal. Not sure if it is safe to enter my credit card details on this website. Version No: 4. when interacting with an information technology system to pursue their need or goal.0 Page 15 of 20 . The results on this screen are tagged with different colors. Assignment 15: User Experience Design Objective: To map the given observations to user experience design issues. Peter Morville has given seven facets of user experience namely 1. 4. you have identified the relevant type of testing needed. it is difficult to understand for people with color blindness.

execution and closure. Activities Project Management Phase Capturing best practices in BoK and submission of BoK (Body of Knowledge) Review of Project Plan Updating the schedule plan due to addition of people to the project Memorandum of Understanding (MoU) sign off and kick start off the project Feedback from all stakeholders to arrive at the best practices Capturing the effort details of the intermediate milestones and analysis Creation of Project code Estimated time: 10 minutes Summary of this assignment: In this assignment. you have mapped the activities to the appropriate project management phases. unlike Version No: 4. QA deals with the process employed to develop and successfully render the product and/or service.0 Page 16 of 20 . QC. Problem Description: Map the following project management activities to the respective project management phases (Initiation/Execution/Closure). Assignment 17: Quality Control and Quality Assurance Objective: To classify the given activities into quality control or quality assurance Background: Quality assurance (QA) refers to the planned and systematic activities implemented in a quality oriented system so that quality requirements for a product or service will be fulfilled. QA ensures “Fitness for purpose”.Infosys Limited Assignments for Software Engineering Assignment 16: Project Management Phases Objective: To map the listed activities to the project management phases Background: Project management consist of three phases namely project initiation. Quality control (QC) is a procedure or a set of procedures intended to ensure that a manufactured product or performed service adheres to a defined set of quality criteria and meets/optimistically exceeds the requirements of the client or customer.

they have proposed a few changes to the process Activity QC/QA 1 2 3 4 Version No: 4.e. During QC activities. They are doing the code-walk-thru of an algorithm 2. John. all these activities belong to the QC phase of ensuring quality as these activities directly ensure that the product i.0 Page 17 of 20 . The template for documenting the requirements for a maintenance project is different from the template for documenting the requirements for new development. He identified “Divide by Zero” defect in the code during Unit testing 6. A team of engineers have done the root cause analysis of the defects identified all along the development of Release 1. Shan is the programmer. Problem Description: Consider the example of food processing systems. For each scenario mentioned below. 5. To prevent such defects occurring in the next release. The training is called as Foundation Program which includes training on IT fundamentals and technology (. etc) training. He is fixing the “Divide by Zero” defect identified by Imran 7.Net. 3. Training the staff in maintaining hygiene. Mainframe. James is the module lead and is the moderator in the meeting. Amit is reviewing the template prepared by Latha 8. identify whether the activity given in the scenario is a QC activity or QA activity. following proper food preparation processes. He is drafting the process to be followed for Reverse Engineering. Imran is a test engineer. Java. Latha has modified the new development requirements template for maintenance project. Testing the taste of the food.Infosys Limited Assignments for Software Engineering QA is the emphasis that is put on the product or service rather than the process that is employed to achieve it. John is the subject matter expert. 4. Carol. Global Education Centre at Infosys Mysore DC provides the training for fresh entrants. conducting sample inspections. food items prepared are delicious and hygienic. checking whether the food items are met with the required quality attributes and rework in case of any discrepancy. Carol is the reader and Mathew is the scribe. Ramesh belongs to the Quality Department. He is carrying out the audit for the configuration management system. building the guidelines & checklists for quality food preparation and auditing the food preparation processes can be treated as QA activities. Mathew and James are having a meeting in a conference Room. Chan belongs to the Audit group. the focus is on the product whereas during QA activities. the focus is on the process. 1.

14 * Radius * Radius. 5. Assignment 18: Defect Classification Objective: To classify the given defects into different defect types Background: Defect detection activities like reviews and testing help in identifying the defects in the artifacts (deliverables). 3. classify the following statements under the defect categories and mention in the table given below. A pointer is declared but not initialized.0 Page 18 of 20 . 6. User interface displays “MALFUNCTION 54” when something goes wrong in the back-end 8. A program designed to handle 1000 simultaneous users.  Logical  User interface  Maintainability  Standards Problem Description: In the context of the above defect categories. Usage of 3. 1.Infosys Limited Assignments for Software Engineering 5 6 7 8 Estimated time: 15 minutes Summary of this assignment: In this assignment. crashed when 1001 th user logged in. No documentation (comments) for the source code Version No: 4. These defects must be classified into various buckets before carrying out the root cause analysis. A “while” loop never exits 7. 3500 lines of code in a single function 4. you have classified the given activities into quality control or quality assurance.14 in the statement Circle_Area = 3. Following are some the defect categories. Divide by Zero Error is not guarded 2. It is used in the program for storing a value.

Schedule.Infosys Limited Assignments for Software Engineering 9. even though the coding guidelines mandate to use Hungarian Notation 10. If the fundamental measures are known. Problem Description: Online loan system has two modules for the two basic services. Background: There are some metrics which are fundamental and the rest can be derived from these. Statement Defect Category 1 2 3 4 5 6 7 8 9 10 Defect Name Estimated time: 15 minutes Summary of this assignment: In this assignment. The two modules have been named as Car_Loan_Module and House_Loan_Module. Defect. Examples of basic (fundamental) measures are Size. House_Loan_Module was completely implemented by John. you have classified the given defects into different defect categories.0 Page 19 of 20 . namely Car loan service and House loan service. House_Loan_Module has 3000 lines of uncommented source code. Version No: 4. Car_Loan_Module was completely implemented by Mike. Hungarian Notation not followed while coding. Car_Loan_Module has 2000 lines of uncommented source code. For example if size and effort are known. Assignment 19: Software Metrics Objective: To understand usage of software metrics. then we can derive others. Pressing of “Tab” key moves the cursor in different fields of a web form randomly. If the total numbers of defects are known we can get the Quality (=defect/size) and so on. we can get Productivity (=size/effort). Effort.

0 Page 20 of 20 . which among the following is an INCORRECT statement? Choose one:     John’s Quality is better than Mike’s Quality John’s Productivity is more than Mike’s Productivity John introduced more defects than Mike John’s Effort is more than Mike’s Effort Estimated time: 10 minutes Summary of this assignment: In this assignment. John’s module had 6 defects. Version No: 4. John took 200 person hours to implement House_Loan_Module. With respect to the context given. you have understood how to use basic and derived quality metrics.Infosys Limited Assignments for Software Engineering Mike took 100 person hours to implement Car_Loan_Module. Mike’s module had 5 defects.