1 / 22

Information Systems Applications 88-275

Information Systems Applications 88-275. Going to the Real World. www.andrew.cmu.edu/course/88-275. Course Meetings: Mondays 11:30-12:20 pm, HH B103 Tuesdays (A21-A) or Thursdays (A20-A)  1:00-2:50pm. 30 minute meeting per team with faculty. Outline. Who we are

liam
Download Presentation

Information Systems Applications 88-275

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Information Systems Applications 88-275 Going to the Real World

  2. www.andrew.cmu.edu/course/88-275 • Course Meetings: • Mondays 11:30-12:20 pm, HH B103 • Tuesdays (A21-A) or Thursdays (A20-A)  1:00-2:50pm. 30 minute meeting per team with faculty.

  3. Outline • Who we are • ISA Goals • Methods of Instruction • Course communication • Calendar • Grading

  4. Who we are • Faculty • Cleotilde Gonzalez • Larry Heimann • Randy S. Weinberg • Administrative assistant • Tracy Crawford

  5. Who we are • Associate Advisors • Jean Alexander • Angie Locknar • Steve Pajewski  • Diana Bajzek • Deborah Lange • Joel Smith • Kim Jordan

  6. ISA GOALS To learn how to build and deliver quality software in a real world development environment

  7. ISA GOALS • Develop software in the real world • This is the closest to the “real world” • Real world is too complex and extensive • Opportunity to compress and simplify the real world

  8. ISA GOALS • Work under uncertainty and time pressure • Total development time: 14 weeks • Sources of uncertainty: • External: clients, project complexity, professor • Internal: team interpersonal conflicts, individual motivation

  9. ISA GOALS • Collaborate and interact in a team environment • Self-managed team • Define roles/responsibilities • Project Manager • Modeling Manager • Quality Manager • Documentation Manager • Team meetings and client-team coordination • Assign tasks to individual team members • Need for real coordination

  10. ISA GOALS • Manage the software development process • Waterfall model provides a framework for planning and scheduling • Course delivery dates based on Waterfall model • Define a client contract • Keep up the planning and control over the development process: DO NOT LEAVE ALL THE BURDEN TO THE PROJECT MANAGER

  11. ISA GOALS • Use, present and explain software development methodologies and procedures • Functional information (case diagrams & narratives), database design, interface design • PRESENT AND EXPLAIN

  12. Methods of instruction • Not a traditional course • Learn by doing • Interactions with Real World • Client: needs, objectives, functional information etc. • Team Work • Faculty are Information Systems advisors

  13. Communication Environment • E-mail & WWW site: www.andrew.cmu.edu/course/88-275 • Regular pre-programmed weekly meetings per team • Occasional Monday meetings

  14. Calendar

  15. Calendar • Total development time: 14 weeks. • Go to the web page • Talk to your teammates • Next meeting: 4:30 to 6:00 client reception at the Schatz Dining Room • You MUST schedule first meeting with your client. • Start working!

  16. Grading • Team Component (100%) • 60% Final evaluation from the client. • 15% Intermediate deliverables. • 25% Final System's evaluation from faculty. • Individual Expectations • Peer-evaluation. • Attendance. -2% for each absence. • Deliverables. -1% per day late.

  17. Grading: Deliverables (15%) • Task and User Analysis. 20% • September 18 • Functional Analysis. 30% • October 9 • Design. 30% • October 30 • Database and Interface as assigned by instructor • Preliminary Usability report. 20% • November 20

  18. Grading: Expectations • 3 Peer evaluations. • Due: September 18, October 30, December 5 • Attendance. 2% for each absence • 2 free absences for weekly meetings • 2% off the FINAL grade for each absence. • Being more than 10 minutes LATE and leaving EARLY will be considered an ABSENCE • Deadlines. 1% off the FINAL grade per day.

  19. Additional deliverables • Draft of client agreements due: September 11. • Final agreements due: October 19. • 1 page progress report: At least 1 day before EACH weekly meeting. • Meeting agenda: At least 1 day before EACH weekly meeting.

  20. Project presentations • Two presentations with the client • October 17 and 19 during team meeting times. • December 8. Project demonstration fair. • Extra review presentations • In-depth team project reviews. • Reserve a Monday meeting time.

  21. Summary • Real software development experience • Learn by doing • Clients • Team interactions • Faculty • Software development methods, procedures, project management

  22. Good luck!! Enjoy the experience

More Related