University of Michigan-Dearborn                         Handed out: 3/24/97
Computer and Information Science Department             Due date: 3/31/97 + TBD
Professor Ken Modesitt                                  Points: 15
CIS 375:  Introduction to Software Engineering          TEAMS: 2 or 3
                        

                                SOFTWARE PROJECT #5
                      INDEPENDENT TESTING AS SUBCONTRACTORS TO CIS 495
                                 JKM & ASSOCIATES

Objectives
• Perform independent code testing on software products being developed by another "company" given the requirements specification and the code
• Develop a useful and working relationship with a software firm (Teams from CIS 495 Capstone Design course of Dr. Maxim)
• Perform SQA on the delivered implementation
• Work in a small team environment
• Make use of existing software engineering standards, as given in the text
• Use project management tools which are relevant to performing as a sub-contractor
• Deliver final testing results to requesting team
• Summarize lessons learned
• Post results on Netforum

Based on the previous successful work of JKM & Associates, we have gained considerable notoriety! In fact, our prowess has even spread to the Capstone Design course (CIS 495) currently being taught by Dr. Maxim. They want our help!

The eight (8) teams of the course are working on individual group projects -- some of which may be submitted to the School of Engineering Design Competition for real $$!! They will provide us with the requirements specification and the code for their project, and want JKM software engineers to test it. The individual CIS 495 teams have different products, team members, due dates, requirements, etc. So part of this class time will be evoted to permitting you time to review the materials they have provided to date.

You will then formulate a contract letter detailing what you plan to deliver, when it will be done, and what resources (including person-hours) you will require. A copy of this letter, with signatures from both teams, will be given to professors of CIS 375 and CIS 495 within one week.

Using what you have learned to date AND from other sources: text, ESE tapes, WWW, Usenet groups, professional literature, and the Compuware guest lecture, etc. you will design the best possible set of tests. You will then execute this test plan with the provided code, recording the results.

One set of deliverables from each of your teams is to be given to the contractors according to the agreed-upon schedule. Two complete sets for the projects are then to be given to the professor, within one class day thereafter.

Each CIS 495 team will then evaluate what you have provided them, and this evaluation will be included in your project grade. Contact with the teams from CIS 495 is required, so be sure to supply and request phone umbers, e-mail, etc. I also plan to set up Netforums for each of the team pairs -- just supply me with the name you would like.

Project Summary
• Select a teammate or two, based on your personal preferences. There must be exactly 8 teams.
• Listen to the overview given by Dr. Maxim today in class
• Review the CIS 495 documents during class; select the top three on which you would like to bid, and notify the instructor ASAP. First come - first serve!
• Take the copy of the document, as assigned
• Develop a SMALL preliminary SPMP
• Begin writing in your logbooks, keeping track of task, problems, resources, hours spent, etc.
• Re-read the existing documentation and determine what questions you have of the CIS 495 team. Ask them for clarification, and cc the JKM CEO, as well as Dr. Maxim (bmaxim@umd.umich.edu)
• Obtain a copy of the code to be tested (URL, disk, etc.), as well as any other required documentation from the CIS 495 team
• Read relevant sections of Chapters 5 and 12 of the text on testing
• Write a formal and signed offer letter, which explicitly lists what you plan to do. This must include the deliverables, schedule and resources. Give two copies to Dr. Modesitt -- one will be passed on to Dr. Maxim and the other one will be commented upon and returned (for inclusion in the final report). This is due in one week -- March 31, 1997.
• Decide on what Netforum name for your team-pairing you would like, and contact Dr. Modesitt to set up one with that name
• Design a preliminary test plan for the code, and conduct a walkthrough. The result should be complete, accurate and unambiguous.
• Execute your test plan, recording the results
• Deliver the reults of the testing, as specified (2 copies) to JKM management for presentation to the CIS 495 teams, according to the agreed-upon schedule
• Contact the CIS 495 team at regular intervals to let them know of your progress -- should be in your contract
• Evaluate the CIS 495 team and the material they provided to you, using a MECCA model
• Complete all documentation, and turn it in

• Software Project Management Plan
• Test design documentation
• Test planning/execution during all phases
• Evaluations of the contractors: as a team and the products they delivered to you
• Evaluations of your teammate
• Lessons learned
• Presentation of results (report, URL, etc.): See attached for format of formal report