Assignments - University of Calgary Webdisk Server
Contents
1. SCHULICH School of Engineering The University of Calgary Department of Electrical and Computer Engineering SENG 521 Software Reliability and Software Quality Project Assignments Behrouz Far Fall 2012 Revision 1 01 Assignment no 1 Software Project Size Workshop Delivery Date October 5th 2012 Friday 4 30 PM Grade 20 of the total labs mark This assignment is a group assignment The team is composed of 2 to 3 members 1 Purpose Measuring Function Point In this assignment you are asked to measure the function point for a typical software system This will help you reinforce the concepts studied during the course 2 Background The overall objective is to determine adjusted function point count for a software system There are several steps necessary to accomplish this The actual sequence or order of steps is not necessary Many counters will complete step 5 throughout the entire count gathering information as they go Determine type of function point count Determine the application boundary 3 Identify and rate transactional function types to determine their contribution to the unadjusted function point count 4 Identify and rate data function types to determine their contribution to the unadjusted function point count 5 Determine the value adjustment factor VAF Calculate the adjusted function point count The unadjusted function point UFP count is determined in steps 3 amp 4 Iti2. etc if needed This can be the same as Assignment 1 Mention and justify any changes if necessary Estimation results for the 3 phases of the model no page limit One page of conclusions and comments including summarizing the results References if any 6 Evaluation Evaluation of the reports is based on the effort the team has put into the project and is measured by mou originality correctness and completeness of the project Notes R 2 Submit one report per team Write your own work only Quotes from articles textbooks and online materials must be properly referenced Reports are evaluated comparatively with the current and previous years reports and other online materials In case of proven plagiarism the assignment will be marked zero and suspected cases will be reported for further investigation Please read the section in the University Calendar on policies described in the Schulich School of Engineering Advising Syllabus available at http schulich ucalgary ca undergraduate advisin Assignment no 3 Defining Necessary Reliability Workshop Delivery Date November 5th 2012 Monday 4 30 PM Grade 20 of the total labs mark This assignment is a group assignment The team is composed of 2 to 3 members Similar to many other projects you start with the requirements analysis and then design However a big difference is that you must first finalize the requirements by defining what fu
3. answer the following questions and complete the following tasks 1 What factors are likely to yield different operational modes for your system Construct a list of possible operational modes Reduce the list to a set of operational modes that are significantly different from each other and frequently executing Limiting the number of operational modes is important otherwise you may create excessive work for yourself later in the software reliability engineering process 2 Pick one operational mode of the product of broad scope and identify its operation initiators The operational mode that you select may be usually the one executed the most in the field And operation initiators may be among user types external systems own system 3 Decide between tabular or graphical representation for the operational profile 4 If you are using the tabular representation list the operations for the operational mode you have selected Consider the different initiators to generate the list for each operational mode 5 If you are using the graphical representation draw the network For large network depending on the size of operations and attributes you may limit the size to not more than 10 operations or attributes or draw part of the network 6 How will you determine occurrence rates and occurrence probabilities for the operational profile of the operational mode you have selected Is it possible to estimate them Can you obtain any dat
4. need to document them all for your own use Include a few 2 5 cases in your report E g one test case for each operation Determine how you will divide hours of test among the associated systems you have defined Determine the number of hours you will devote to feature regression if needed and load test for the product 11 8 9 Allocate the hours of load integration test among the operational modes Run your program and execute run the test for one operational mode You may need to write some scripts to select cases at random run them and record the output To do so you must have your code be ready and stable Note If you have not implemented the project ask the TA to provide you with sample test data 10 Use a reliability growth tool such as CASRE to verify the actual reliability growth 11 Determine whether you have achieved your target and may may not release your software If the answer is yes explain why If the answer is no what do you suggest Reduce functions Postpone release Add additional test cases Do more testing Drop the project Deliverables 1 2 3 4 5 6 7 Title page project title delivery date team members name student ID and email One page executive summary The documented test profile s This document provides answer to the above mentioned questions and completion of the above mentioned tasks Report on the failures detected for the operational mode the tes
5. Solaris 2 x Linux etc find the failure intensity for that platform if you can Check if the maker gives the FI for its product If not try to guess or use the values given in the textbook 5 Determine the product developed software failure intensity objective if applicable Straightforward by subtracting platform s FIO from target FIO However if you start by dividing your project into a number of independent modules you should define FIO for each module and then add them up 6 How will you balance fault prevention fault removal and fault tolerance strategies Consider your specific requirements for reliability timely delivery and cost and allocate your resource percentages among the following six activities You may add other activities to the list if they are significant but the percentages must total 100 E Fault prevention Requirements reviews Design reviews E Fault removal Code inspection Unit test System test E Fault tolerance design for fault tolerance If you select fault prevention as the main strategy you should demonstrate how you could adopt the ISO 9000 3 guidelines in your project If you select fault tolerance you should start your design to account for fault tolerance i e redundant modules etc Write a summary of your selected strategies and how you are going to implement them Deliverables 1 Title page project title delivery date team members name student ID and email 2 One page execu
6. a from already available resources log files etc Can you measure or collect data In either case represent the occurrence probabilities using simple numbers Deliverables 1 Title page project title delivery date team members name student ID and email 2 One page executive summary 3 Project specification 1 2 pages clearly mentioning what is included system functions modules and support systems DB server Web server etc if needed This can be the same as Assignment 1 Mention and justify any changes if necessary 4 The documented operational mode s and operational profile s This document provides answer to the above mentioned questions and completion of the above mentioned tasks 5 References if any Notes 1 Submit one report per team 2 Write your own work only Quotes from articles textbooks and online materials must be properly referenced Reports are evaluated comparatively with the current and previous years reports and other online materials In case of proven plagiarism the assignment will be marked zero and suspected cases will be reported for further investigation Please read the section in the University Calendar on policies described in the Schulich School of Engineering Advising Syllabus available at http schulich ucalgary ca undergraduate advisin 10 Assignment no 5 Prepare Execute Test and Release Workshop Delivery Date December 3rd 2012 Monday 4 30 PM Grade 20 of t
7. he total labs mark This assignment is a group assignment The team is composed of 2 to 3 members At this stage you identify how many test cases you need how much time you want to spend on testing the product and finally define your test cases and develop your test suite You must perform the following tasks 1 2 3 4 5 6 7 Estimate the number of test cases you need to prepare If this is the first release estimate the total number of test cases required If this is not the first release estimate the number of new test cases for this release Your estimation can be based on time and or cost criteria Allocate the number of test cases among the associated and sub systems to be tested How many new test cases should be created if this is not the first release How many test cases will go to the other infra structure systems How many to the OS How many will be assigned to the acquired and developed products Allocate the number of test cases for the developed product to its operations Make sure you identify critical operations properly and assign enough test cases to them New test cases will naturally be assigned to new operations in the first and subsequent releases Specify the test profile for one of the operational modes If you have more than one operational mode e g prime time peak off time etc select the one most frequently used and specify its test profile Document your test cases You
8. is composed of 2 to 3 members 1 Purpose Measuring Effort Using Software Metrics Tools In this assignment you are asked to measure software cost and effort for a realistic project using COCOMO II tool This will help you reinforce the concepts studied during the course 2 Tools The tool based on Constructive Cost Model COCOMO II 3 Background COCOMO II includes three stage series of models 1 The earliest phases will generally involve prototyping using the Application Composition model capabilities 2 The next phases will generally involve exploration of architectural alternatives or incremental development strategies To support these activities COCOMO II provides an early estimation model called the Early Design model 3 Once the project is ready to develop it should have a life cycle architecture which provides more accurate information on cost driver inputs and enables more accurate cost estimates To support this stage COCOMO II provides the Post Architecture model The Application Composition model is used in estimating early stage issues where source code is not available It uses counts entities such as user interfaces software system interaction to measure Object Points OP and then use the following relation to derive the effort E E OP PROD where OP is the object point PROD is the productivity rate defined below Developers experience and capability Very High The Early Design model
9. is used to evaluate alternative software system architectures and concepts of operation An unadjusted function point count UFC is used for sizing This value is converted to KLOC The Early Design model equation is E 2 45 x KLOC x EAF The KLOC may be computed using the COCOMO II tool or by converting the object point to KLOC The effort adjustment factor EAF is calculated as using 7 cost drivers Description Counterpart Combined Post Architecture Cost Driver Product reliability and complexity RELY DATA CPLX DOCU Required reuse Platform difficulty IME STOR PVOL Personnel capability ACAP PCAP PCON Personnel experience AEXP PEXP LTEX Facilities OOL SITE Schedule CED The Post Architecture model is used during the actual development and maintenance of a product The Post Architecture model includes a set of 17 cost drivers and a set of 5 scale factors determining the projects scaling component The Post Architecture model equation is E 2 45x KLOC xEAF b 0 91 0 019 SF j l The SF and EAF can be calculated using the default values given by the COCOMO II tool Additional documents related to COCOMO II tool and user manual can be downloaded from 1 Original manuals and documents for COCOMO Project document repository http sunset usc edu research COCOMOII index html 2 COCOMO II Model Manual local copy http www enel ucalgary ca People far Lectures SENG421 PDF COCOMO modelman pdf 3 COCOMO II User Manua
10. l local copy http www enel ucalgary ca People far Lectures SENG421 PDF COCOMO userman pdf 4 Scenario Suppose that your group is a software development team assigned to build one of the projects listed on suggested project list Appendix Page You are supposed to measure the total effort required to build the project You may proceed as follows 1 Start with defining the requirements for your project Note that you should proceed to the extent that the detailed requirements are sufficient to measure the object points or function points Read the COCOMO II user manual available as a help file on the Windows system and also as a separate PDF file and run the tool Start with defining a new project and define modules that you defined in Step 1 and proceed through the 3 phases to refine your estimation of effort Note that sometimes you may need to revise earlier stage decisions and repeat estimation to avoid conflicts Try to change a few parameters like project duration risk etc and how they may affect your original estimations Use the reporting tool of COCOMO II to generate report pages 5 Deliverables Your deliverable report should consist of 1 2 3 Title page project title delivery date team members name student ID and email One page executive summary Project specification 1 2 pages clearly mentioning what is included system functions modules and support systems DB server Web server
11. nctions the system offers functional requirements together with what reliability criteria must be satisfied non functional requirements In this assignment the focus is on the latter which is usually ignored in conventional requirements analysis To do so you must concentrate on defining the necessary reliability for the product You can have a better understanding of the reliability centered requirements by answering the following questions 1 How will you define failure for the product by severity class as product specific as possible Answer in detail what the failures that you expect the system handle are and how severe they may be 2 Choose the natural or time unit you will use for the product Explain why you select such unit s and how to convert one to the other if you have more than one measurement unit Time unit is useful when the operations of the system can be measured with respect to time e g a server must be up 98 of running time Other units such as number of transactions jobs etc may be used otherwise 3 Set the product failure intensity objective FIO Define FIO target for your product If impossible to define it now leave it open for a later stage 4 Find the expected product acquired failure intensity based on the failure intensities of the hardware and acquired software components if applicable Check whether your software should run on a specific platform IBM PC Windows xx or SUN Sparc
12. s not important if step 3 or step 4 is completed first In GUI and OO type applications it is easy to begin with step 3 The final function point count adjusted function point count is a combination of both unadjusted function point count UFP and the general system characteristics GSC s 3 Scenario Suppose that your group is a software development team assigned to build one of the projects listed on suggested project list Appendix Page You are supposed to measure the Function Point for this project You may proceed as follows 1 Start with defining the requirements for your project Note that you should proceed to the extent that the detailed requirements are sufficient to measure the function points Read relevant sections of the Function Points Analysis Training Course 110 Pages by David Longstreet David SoftwareMetrics com www SoftwareMetrics com This document is downloadable from course web page The document is a step by step guide to measure FP Follow the steps mentioned there Many of the concepts can only be comprehended and decided through the discussion among the team members 4 Deliverables Your deliverable report should consist of 1 2 3 6 Title page project title delivery date team members name student ID and email One page executive summary Project specification 1 2 pages clearly mentioning what is included system functions modules and support systems DB ser
13. t was running CASRE reliability growth report Release recommendation document References if any Notes 1 Submit one report per team 2 Write your own work only Quotes from articles textbooks and online materials must be properly referenced Reports are evaluated comparatively with the current and previous years reports and other online materials In case of proven plagiarism the assignment will be marked zero and suspected cases will be reported for further investigation Please read the section in the University Calendar on policies described in the Schulich School of Engineering Advising Syllabus available at http schulich ucalgary ca undergraduate advisin 12 Appendix Suggested Project List SENG 521 You need to bring a software system of reasonable size more than 5KLOC C or equivalent to use it as your project for SENG 521 This may be a software system that you have already developed and tested e g for ENSF 409 or SENG 437 Having a test suite attached to the source code is a nice to have feature and can save you time and effort You can also look into the Apache foundation s http www apache org GNU s http www gnu org and SourceForge s http sourceforge net projects to select an appropriate project You must define your project in the first two weeks of the Course and consult with the TA regarding the depth and scope of the project and obtain his her approval 13
14. tive summary 3 Project specification 1 2 pages clearly mentioning what is included system functions modules and support systems DB server Web server etc if needed This can be the same as Assignment 1 Mention and justify any changes if necessary 4 Reliability requirements document containing answers to the above questions 5 References if any Notes 1 Submit one report per team 2 Write your own work only Quotes from articles textbooks and online materials must be properly referenced Reports are evaluated comparatively with the current and previous years reports and other online materials In case of proven plagiarism the assignment will be marked zero and suspected cases will be reported for further investigation Please read the section in the University Calendar on policies described in the Schulich School of Engineering Advising Syllabus available at http schulich ucalgary ca undergraduate advisin Assignment no 4 Developing Operational Profiles Delivery Date November 19th 2012 Monday 4 30 PM Grade 20 of the total labs mark This assignment is a group assignment The team is composed of 2 to 3 members Here we go one step ahead and define the modes and profile of operation for the developed software In real life projects you should also finalize the analysis and design and start developing your code at this stage The code will be used later during the running test phase Assignment 5 You should
15. ver Web server etc if needed FP measurement results for the different modules and overall project including description and justification for VAFs no page limit One page of conclusions and comments including a Conclusions related to the project summarizing the results b Your comments related to this assignment Your own viewpoint related to the assignment What do you think about this assignment Was it useful How can it be improved etc List of references if any 5 Evaluation Evaluation of the reports is based on the effort the team has put into the project and is measured by mou originality correctness and completeness of the project Notes R 2 Submit one report per team Write your own work only Quotes from articles textbooks and online materials must be properly referenced Reports are evaluated comparatively with the current and previous years reports and other online materials In case of proven plagiarism the assignment will be marked zero and suspected cases will be reported for further investigation Please read the section in the University Calendar on policies described in the Schulich School of Engineering Advising Syllabus available at http schulich ucalgary ca undergraduate advising Assignment no 2 Software Project Time and Effort Workshop Deadline October 22th 2012 Monday 4 30 PM Grade 20 of the total lab marks This assignment is a group assignment The team
Download Pdf Manuals
Related Search