University of Michigan-Dearborn                         Handed out: 1/27/97
Computer and Information Science Department             Due date:  2/7, 2/10, 2/12
Professor Ken Modesitt                                  Points: 5+10 
CIS 375:  Introduction to Software Engineering          Individual + Team

SOFTWARE PROJECT #2
SOFTWARE DEVELOPMENT TEAM SELECTION
PART I: "ON-CAMPUS" INTERVIEW
PART II: "IN-PLANT" TECHNICAL INTERVIEW

Objectives
1. Participate in two mock interviews
2. Summarize lessons learned
3. Prepare to:
-engage in "real-world" software development, maintenance and reverse software engineering processes,
involving design and analysis
-use a simple CASE tool
-perform risk analysis on existing project
-work with a team involving a project manager

Context of Project
JKM & Associates is a ten-year old company based in New York whose primary customer base is higher education. They are looking for some qualified entry-level software engineers to help with the maintenance of several software projects currently underway at the University of Michigan-Dearborn, one of their primary accounts. Samples include desktop video-conferencing, WWW campus navigation systems, a virtual tour of ELB, the "automatic" creation of E-mail distribution lists, and home pages for the UM-Dearborn Fact Book and the UM-Dearborn Graduate Studies Program. Some evaluations of CASE tools will also be performed for internal consideration.

Background
Students in this course from earlier semesters and other courses have designed and coded a number of software products. You will have first-hand experience with these versions and so can determine their strengths and weaknesses in future projects for this course.

Project Summary
Interview for a company engaged in software development for universities. This will be for the position of an entry-level software engineer with JKM & Associates.

PART I: ON-CAMPUS INTERVIEW [Weeks of January 27 - February 7]

    {Roles played: Prospective new-hire}
  1. Set up an 20-minute interview with JKM & Associates via Mrs. Loretta Thiry (lthiry@umdsun2.umd.umich.edu or 436-9145). Be sure to tell her it is for the CIS 375 class. Give her the URL of your home page at the same time. When you come by, ask for a copy of the application form. Currently, we have ones from the following CIS Professional Advisory Board members (just pretend they are from JKM!): CBSI, Chrysler, Coopers & Lybrand, and Ford.
  2. You may wish to look at the list of types of positions for which your skills be used (see attached).
  3. Fill out an application. You will be role-playing a graduating senior seeking full-time employment.
  4. At least two hours prior to the interview, bring a cover letter, the completed application and your resume to Mrs. Thiry. I would "assume" you would use the resume you posted from Project #1: make sure it has a date on it! How about using career services office for help (e-mail, home page, GPA, UPE/ACM, teams, courses, goals)?
  5. At the interview time, please bring at least one sample of your "best" software product, or the one with which you are most proud. This can be a physical entity which uses your software, the complete documentation package (manuals, code, etc.), or some other manifestation. Please do not bring just a listing!

PART II: IN-PLANT INTERVIEW [February 10]
THIS WILL BE VIDEO-TAPED. Roles played: Prospective new-hire and existing team member of software team.

    {As existing team member}
  1. Prepare a set of at least 10 questions you would pose to a prospective new hire. Do not ask trivial ones you already know from the resumes. No "give-aways!" Follow up your questions with requests for examples. Make sure to include technical queries, as well as ones which would be helpful in selecting a team member.
  2. Post this set by Friday, February 7, on netforum under "Project 2: Interview questions." Be sure to have them appear under your name as a message -- NOT a reply!
  3. Review resume of prospective new hires. You already have this from project #1.
  4. Interview 8 applicants for the position of helping you maintain and develop software for a university environment.
  5. Use at least 7 of your questions when interviewing the applicants, However, you may want to change some of your questions after hearing those of your teammates. Make sure to record such questions -- will be posted later.
  6. After the interviews are concluded {NLT COB, February 11} post the position you would recommend for each candidate on netforum under "Project 2- Recommended positions." Be sure to include yourself! E-mail me the names of those students with whom you would prefer not to work in a team project, e.g., schedule conflicts.

By COB 2/12, Post on netforum "Lessons Learned" as "Project 2 ": Applicant: and "Project 2: Staff." Include those "dynamic" questions mentioned above.

Remember to use your logbook.

Textbook References
Chapter 2: The Software Process and Its Problems
Chapter 3: Software LifeCycle Models
Chapter 12:Implementation Phase, esp. 12.6-12.9