SE 101 Freshman Seminar

Week 5 - Interview Assignment Introduction, Meetings, and Teams

Class Plan:

1.     Introduction of Interview Assignment (10 minutes)
See the section on the Long Term Activity for details.

2.     Teaming activity and report (30 minutes)

3.     Teams - Potential and Pitfalls (25 minutes)

4.     Lego House Activity (35 minutes)

5.     Wrap up discussion of teaming and requirements (10 minutes)

Activities:

The class will be divided into teams of no less than 5 students, and each team will work together for both class activities.

For the first activity students will gather as a group and head to the team rooms. Each team is chartered to discuss the challenges that may arise when communicating with a customer during requirements gathering.  Each team must compile a list and create a report to be discussed in class.

Once time has elapsed, all teams will return to the classroom for discussion.

 

The second activity's goal is for each team to build a Lego house meeting the requirements of a customer (represented by your instructor). The rules for how requirements are determined will be outlined as part of the activity set up.

Homework for Next Time:

  1. Read the Software Engineering Code of Ethics and Professional Practice (both the short and long versions).
  2. Scour Wallace Library and the web for ethics codes used by other institutions and professions (including other engineering disciplines). In a Word or PDF document, list the titles and locations (either a book reference or a URL) for 3-5 such codes. Follow the list with a brief (1-2 paragraph) description the commonalities and differences among the various codes. Submit the document to the Homework - Week 5 dropbox by noon on next Wednesday.

Long Term Activity - Interview With a Software Professional (20% of your final grade):

  1. Each student must identify and interview a professional in the software field, preferably a software engineer or first level manager, about the professional's take on the field of software development. Be sure to take adequate notes, as these will be the basis for your final report. Issues you should address include (but are not limited to) the following:

a.      Your interviewee's name, email, and city of residence.

b.     The companies the interviewee has worked for, including the current employer and length of service there.

c.      The interviewee's position (or title) and the types of software systems he or she works on.

d.     What is the size of the team the interviewee works on or manages?

e.      What technologies are employed: languages, databases, and tools for areas such as configuration management, testing, automated build.

f.       What is typical workday like?

g.      What are the most important skills needed to succeed in the job?

2.     To find potential interviewees, brainstorm sources (e.g., friends and relatives, blogs on the Web). You may not interview RIT faculty members or members of your family.

3.     There is an Interview Paper discussion group on myCourses where each student is to post the name and affiliation of the person selected by class on the Friday of the 7th week. To prevent overburdening any particular professional, only one student can interview any specific person. In the case of duplication, the first person to post to the discussion group wins.

4.     If you cannot connect with someone by the end of the week 7, your instructor may be able to help: We have a small set of alumni who have agreed to be interviewed. It is much preferred, however, that you find your own interviewee.

5.     Submit the following on or before the Sunday before finals week:

a.      A 2-4 page paper summarizing your interview (as either a Word or PDF file).

                                                        i.            Use 1" top and bottom margins, 1.25" side margins, and a 12 point font.

                                                      ii.            The header of each page must contain your name and the page number.

                                                    iii.            The lead paragraph must clearly state who you interviewed, their company or organization, and their title or position.

                                                   iv.            You will be assessed on the paper's content and mechanics (organization, grammar and spelling).

b.     A copy of the notes, interview transcripts, email exchanges, and any other material used in writing your paper (captured in either a Word or PDF file).

6.     Bring a hard copy version of your paper to the final exam, where it will provide a foundation for discussions.