SE604 Software Testing and QA Lecture #2: Contract Review Lecture #3: SQA Planning .

1. SE604Software Testing and QALecture #2: Contract Review Lecture #3: SQA Planning . Slides by Mohammad El-Ramly, PhD http://www.acadox.com/class/48453 MRABFH

2. حديث شريف • إن الله يحب إذا عمل أحدكم عملا أن يتقنه • إن الله كتب الإحسان على كل شئ

3. Course Organization • Fundamentals of SW Quality Assurance 4~5 wks 2. Software Vulnerabilities 1~2 wks Guest 3- Software Testing 4~5 wks Guest / Me 4- Presentations 1~2 wks Students

4. Assessment • 40% Coursework A1=5 + A2=7 + A3~=6 • 10% Midterm • 50% Final

5. Lecture 2 Outline • Pre-project QA Activities • Contract Review • QA Planning • Assignment #2 • Assignment #1 presentations

6. Techniques for Improving SW Quality (Code Complete) • SW Q Objectives & Planning • Explicit QA Activities • Testing Strategy • SE Guidelines • Formal / Informal Technical Reviews • Change-control Procedures • Measurement of Results • Prototyping

8. Assignment 1 – 5 marks • Due 30 Sep 2017 @ 8 am • Write 6 pages of font 12, single spaced • Header, title, etc. • P1 – Introduce yourself, your study and your experience. • P2&3 – Summarize the most important points in readings of week 1. • P4&5&6 – Interview 3 developers / managers in 3 companies about (1) what they do, (2) what process they follow and (3) QA activities they do • Prepare 6-min prez on your report. • Upload in acadox by deadline.

9. Notes on Assignment 1 • Name files properly: • SE604-MohamedAli-Assignemnt1-Presentation • Follow instructions closely • Every file should have a proper header. • You should learn technical writing • Follow format or template • Cairo not cairo • Use font 24 or 28 minimum for slides • Use presentation template • Presentation means ppt or prez or others

11. Assignment 2 – 7 marks • Due 7 & 10 & 14 Oct 2017 @ 8 am • Read the sample contracts @ acadox. • Read chapters 5 and 6. • Read carefully proposal / contract review check list. • Here are some links also. Share any better links you find with the class. • http://www.swalif.net/softs/swalif54/softs143978/ • https://www.traidnt.net/vb/traidnt2284258/ • Identify the main parts that a SW development contract should have. • Do you have a group of any kind ?

12. Assignment 2 – 7 marks • Assume a system whose requirements are not less than three pages. You can get it from the net and share it with others. • By 7 Oct 2017 @ 8 am submit a contact for implementing this software. (3 marks) • By 10 Oct 2017 @ 8 am submit a review of another contract that you will be assigned by the Dr. (2 marks) • By 14 Oct. 2017 @ 8 am submit final version of the contract after implementing the comments in the review & explain what you changed. (2 marks) • Follow the instructions on next page carefully.

13. Assignment 2 – Draft Contract • سيكتب العقد باللغة العربية • ستفترض عميلا يريد تنفيذ هذا البرنامج و أنت الشركة المطورة له • لا يقل العقد عن 5 صفح فونت 12 و مسافة واحدة + صفحة غلاف فيها البيانات الأساسية و ايميلك و هاتفك • سيلحق بالعقد كملحق مواصفات البرنامج المطلوب • يكتب العقد بصيغة واضحة و تنسيق جيد و لغة سليمة • العقد الجيد يغطى كل المتعلقات بتنفيذ البرنامج ، على سبيل المثال لا الحصر: • اسم الشركة و العميل و مقرهما ، تعريفات ، المواصفات المطلوبة و مراجعتها و اعتمادها ، الاعمال المطلوبة و الجدول الزمنى ، السعر و المدفوعات ، كيفية التعامل مع التعديلات ، خدمات ما بعد البيع من صيانة و تدريب و تدشين ، ملكية البرنامج و الترخيصات و حق بيعه ثانية ، الضمان ضد العيوب ، المسؤولية لو فيه جزء منه مسروق من آخرين ، انهاء المشروع بشكل سليم أو فى حالة النزاع ، المحكمة المختصة ، الخصوصية ‘ إلخ. • يمكنك استشارة محامى لو لديك صلة بأحدهم • يتم تخزين العقد فى ملفى بى دى اف بالاسم التالى و رفعه على أكادوكس • SE604-Assignment2-InitialContract-YourName

14. Assignment 2 – Contract Review • ستقوم بمراجعة عقد أحد الزملاء الذى سأخصصه لك • قم مراجعة جيدة و متعمقة على أكمل وجه فى ضوء مواصفات البرنامج المقترحة • انظر هل يغطى العقد كل الاجزاء المطلوبة و استخدم Review Checklists • لا تقل المراجعة عن صفحتين فونت 12 و مسافة واحدة + صفحة غلاف فيها البيانات الأساسية و ايميلك و هاتفك و بيانات العقد الذى تراجعه • يتم تخزين العقد فى ملفى بى دى اف بالاسم التالى و رفعه على أكادوكس و ارساله لصاحب الملف الأصلى أيضا • SE604-Assignment2-ContractReview-ReviewerName

15. Assignment 2 – Final Contract • ستقرأ المراجعات جيدا و تقوم بتنفيذ اهم ما فيها • ستعد نسخة معدلة من العقدمع اضافة (1) سكشن يذكر فيه ما الذى تم تغييره و (2) المصادر المستعملة. • يتم تخزين العقد الجديد فى ملفى بى دى اف بالاسم التالى • SE604-Assignment2-FinalContract-YourName • سترفع على أكادوكس ملف مضغوط اسمه كالتالى • SE604-Assignment2-YourName • يحتوى على الملفات الثلاثة ، العقد الأولى ، و المراجعة التى عملها زميلك و العقد النهائى كلها بصورة بى دى اف • SE604-Assignment2-InitialContract-YourName • SE604-Assignment2-ContractReview-ReviewerName • SE604-Assignment2-FinalContract-YourName

16. Assignment 2 – Important Notes • بعض الطلاب سلم عقدا كاملا جاهزا حصل عليه من أى مصدر و عليه حتى اسم العميل و اسم المطور !! • ما هى الدرجة التى تتوقعها على ذلك ؟؟ • كل ما يتم تسليمه يجب أن يكون أصليا من عمل الطالب من الألف للياء و تم إعداده حصريا لهذا المقرر. • عند الحاجة الضرورية للنقل من أى مصدر ، يجب أن يتم النص على ذلك صراحة مع ذكر المصدر فى قائمة المصادر. • لو قمت بذلك لديك يومان لتعديل هذا الخطأ. • و يجب على جميع الطلاب ذكر كافة المصادر المستعملة فى نهاية العقد النهائى مع روابطها.

19. Change and Configuration Management Software Quality Landscape Reviews Collaborative Development / Reviews Requirements V & V Guidelines, Standards and Templates Design Review Bug Tracking Surveys Contract Review QA Planning and Budgeting Testing Metrics Secure Coding Debugging Refactoring Deployment & Maintenance Planning Design Testing Requirements Development M a n a g e m e n t

20. Change and Configuration Management Software Quality Landscape Reviews Collaborative Development / Reviews Requirements V & V Guidelines, Standards and Templates Design Review Bug Tracking Surveys Contract Review QA Planning and Budgeting Testing Metrics Secure Coding Secure Coding Debugging Refactoring Deployment & Maintenance Planning Design Testing Requirements Development M a n a g e m e n t

21. Pre-project QA So, it is natural to start QA before project. • Contract review • Draft Proposal Review • Draft Contract Review • Planning and budgeting

22. Ch 5 Outline: Contract Review • Introduction • Contract Review Process • Objectives of Contract Review • Implementation of Contract Review

23. Ch 6 Outline: QA Plan • Development & quality plans objectives • Elements of the development plan • Elements of the quality plan • Development and quality plans for small and for internal projects • SW development risks / risk management

24. 1. Intro • A badcontract is always an undesirable event. • Involves • Loosely defined requirements • Unrealistic schedules and budgets • Hidden clauses • Will result in poor quality SW and project loss.

25. Carnegie Fruits and Vegetables Project • CFV project team finished on schedule • 10 months project • System registers product receipts from growers, processes clients’ orders, and produce shipments to clients, bills clients, and calculates payments made to the growers. 4. Client staff are to be trained on site

26. Contracts come from ….. • Participation in a tender. • Submission of a proposal according to the customer’s RFP. • Receipt of an order from a company’s customer. • Receipt of an internal request or order from another department in the organization.

27. 2. The Contract Review Process • Contract review is the SQA component devised to guide review drafts of proposal and contract documents. • If applicable, contract review also provides oversight of the contacts carried out with potential project partners and subcontractors.

28. The Contract Review Process • The review process itself is conducted in two stages: • Stage One – Review of the proposal draft prior to submission to the potential customer (“proposal draft review”). • Stage Two – Review of contract draft prior to signing (“contract draft review”).

29. I. Proposal Review • This stage reviews the final proposaldraftand the proposal’s foundations: • customer’s requirement documents, • customer’s additional details and explanations of the requirements, • cost and resources estimates, • existing contracts or contract drafts of the supplier with partners and subcontractors.

30. Checklist

31. Checklist

32. Checklist

33. II. Contract Review • This stage reviews the contract draft on the basis of the proposaland the understandings (including changes) reached during the contract negotiations sessions.

34. Checklist

35. 3. Proposal Draft Review Objectives • Customer requirements have been clarified and documented. • Alternativeapproaches for carrying out the project have been examined. • Software reuse, • Partnerships or subcontracting with firms with specialized knowledge or staff.

36. 3. Proposal Draft Review Objectives • Formal aspects of the relationship between the customer and the software firm have been specified. • Communication and interface channels. • Deliverables and acceptance criteria. • Formal Approval process

37. 3. Proposal Draft Review Objectives • Identification of development risks. • Adequate estimation of project resources and timetable. • Professional staff • Project’s budget, • Including subcontractors’ fees. • Scheduling estimates (including all parties)

38. 3. Proposal Draft Review Objectives • Examination of the company’s capacity with respect to the project. • Examination of the customer’s capacity to meet his commitments. • Finances • Installing required H/W, S/W, Communication • Hiring required skills.

39. 3. Proposal Draft Review Objectives • Definition of partner and subcontractor participation. • Quality assurance issues, • Payment schedules, • Distribution of project income/profits, • Cooperation between PM and teams. • Definition and protection of IP rights. • License to reuse existing S/W • Future ownership of the SW

40. 3. Contract Draft Review Objectives • No unclarified issues remain • All the understandings reached between the customer and the firm are to be fully and correctlydocumented in the contract and its appendices • No changes, additions, or omissions that have not been discussed and agreed upon should be introduced into the contract draft

42. 4. Implementation of Contract Review • Contract reviews vary in their magnitude • Magnitude varies depending on project characteristics and magnitude and complexity.

43. Factors affecting the extent of a contract review • Project magnitude, man-month • Project technical complexity. • Degree of staff acquaintance with and experience in the project area. • Project organizational complexity. (i.e., for partners, subcontractors, and customers)

44. Who performs a contract review? • The leader or another member of the proposal team. • The members of the proposal team. • An outside professional or a company staff member who is not a member of the proposal team. • A team of outsideexperts.

45. Contract review for a major proposal • Very large-scale project, • Very high technical complexity, • New professional area for the company, • High organizational complexity

46. Difficulties of contract review CR for a major proposal • Time pressures (in a few days during tender process) • Requires professional experience • Usually done by senior busy staff

47. Tips for contract review CR for a major proposal • Schedule CR time in proposal writing • A team should carry out the contract review • A contract review team leader should be appointed • Recruitment of the team members • Distribution of review tasks • Coordination between the members • Follow-up of activities

48. Contract reviews for internal projects • IT department serving others • Not formal customer-supplier relation • Mild or brief review is usually done