information systems applications 88 275
Download
Skip this Video
Download Presentation
Information Systems Applications 88-275

Loading in 2 Seconds...

play fullscreen
1 / 22

information systems applications 88-275 - PowerPoint PPT Presentation


  • 165 Views
  • Uploaded on

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

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'information systems applications 88-275' - liam


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
www andrew cmu edu course 88 275
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
Outline
  • Who we are
  • ISA Goals
  • Methods of Instruction
  • Course communication
  • Calendar
  • Grading
who we are
Who we are
  • Faculty
    • Cleotilde Gonzalez
    • Larry Heimann
    • Randy S. Weinberg
  • Administrative assistant
    • Tracy Crawford
who we are1
Who we are
  • Associate Advisors
    • Jean Alexander
    • Angie Locknar
    • Steve Pajewski 
    • Diana Bajzek
    • Deborah Lange
    • Joel Smith
    • Kim Jordan
isa goals
ISA GOALS

To learn how to build and deliver quality software in a real world development environment

isa goals1
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
isa goals2
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
isa goals3
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
isa goals4
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
isa goals5
ISA GOALS
  • Use, present and explain software development methodologies and procedures
    • Functional information (case diagrams & narratives), database design, interface design
    • PRESENT AND EXPLAIN
methods of instruction
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
communication environment
Communication Environment
  • E-mail & WWW site: www.andrew.cmu.edu/course/88-275
  • Regular pre-programmed weekly meetings per team
  • Occasional Monday meetings
calendar1
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!
grading
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.
grading deliverables 15
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
grading expectations
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.
additional deliverables
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.
project presentations
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.
summary
Summary
  • Real software development experience
  • Learn by doing
    • Clients
    • Team interactions
    • Faculty
    • Software development methods, procedures, project management
good luck

Good luck!!

Enjoy the experience

ad