csse 371 372 software requirements and specification software project management n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
CSSE 371/372 – Software Requirements and Specification/Software Project Management PowerPoint Presentation
Download Presentation
CSSE 371/372 – Software Requirements and Specification/Software Project Management

Loading in 2 Seconds...

play fullscreen
1 / 22

CSSE 371/372 – Software Requirements and Specification/Software Project Management - PowerPoint PPT Presentation


  • 139 Views
  • Uploaded on

CSSE 371/372 – Software Requirements and Specification/Software Project Management. Steve Chenoweth/Sriram Mohan RHIT. Introductions. Name Major Hometown An interesting fact about you that others at Rose probably don’t know. Course Overview. Materials on Angel Syllabus Schedule.

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 'CSSE 371/372 – Software Requirements and Specification/Software Project Management' - evangeline-pugh


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
csse 371 372 software requirements and specification software project management

CSSE 371/372 – Software Requirements and Specification/Software Project Management

Steve Chenoweth/Sriram Mohan

RHIT

introductions
Introductions
  • Name
  • Major
  • Hometown
  • An interesting fact about you that others at Rose probably don’t know
course overview
Course Overview
  • Materials on Angel
  • Syllabus
  • Schedule
general themes
General Themes
  • How do we interact with clients to obtain requirements?
  • How do we use the requirements to design the software?
  • How do we use the requirements to verify client needs?
  • How do we use the requirements to design the interaction?
  • How do we plan, monitor and control a project?

Project versus Lecture

general info
General Info
  • Books - 371
    • Managing Software Requirements: A Use Case Approach, Second Edition, by Dean Leffingwell and Don Widrig
    • Interaction Design: beyond human-computer interaction, Second Edition, by Jennifer Preece, Yvonne Rogers and Helen Sharp
  • Books – 372
    • Effective Project Management: Traditional, Adaptive, Extreme, Fourth Edition by Robert K. Wysocki, (paperback)
  • Case Studies
  • Office Hours
course components
Course Components
  • Project
    • This is the most important part of the learning experience
    • 5 Milestones (Typically due on Friday)
    • 50% of the grade
  • Exams
    • 20% of the grade
    • Two mid-terms(No Finals)
  • Assignments
    • 9 in 371, 8 in 372 (Typically Due on Tuesday and Friday)
    • 9 Case Studies (Typically on Friday, Monday)
    • 20% of the grade
  • Class Interaction/Quizzes/In-Class Activities
    • 10%
project1
Project
  • Real clients with real needs
  • Simulate the real world
  • Teams
    • Each team will have 3 students.
    • Management assigned
  • Project Managers
    • Derek Baker
    • Sam Green
    • Tyler Gonnsen
    • Andrew Houvener
    • Jarrod Stormo
presentations
Presentations
  • Client Presentation
  • Post partum presentation
team activities
Team Activities
  • Meet with client once a week
  • Meet with project manager once a week
  • Meet regularly
  • Plan
  • Use your project manager and instructors expertise.

Plan ahead

team roles
Team Roles
  • Secretary
  • Contacts
    • Manager
    • Instructor
    • Client
  • Tasks
    • Assigner
    • Monitor
  • Librarian
  • Guru
weekly assessment report
Weekly Assessment Report
  • Due weekly to the PM and Primary Instructor
    • PM – 12 hours before Meeting
    • Instructor – Friday at Noon(Hard Copy)
  • It records
    • Weekly Status
    • Tasks to be completed next week
      • High Level Summary
      • Who is responsible for them?
    • Tasks completed last week(same as above)
    • Key issues and problems(include a mitigation strategy)
    • Weekly Metrics(hours of work estimated, actual and variance from previous weeks and total to date)
project manager
Project Manager
  • Assist the team with process
  • Supervisory role
  • Review teams artifacts
  • Evaluate teams performance
    • Can recommend that a team member be fired
writing
Writing
  • Professionally written
    • No slang, chat lingo …
    • Free of grammatical and spelling errors
    • Well organized
    • Thorough and complete
  • Must be submitted to supervisor before final submission
  • Each team member must approve the submission.
  • Use the learning center

We will be happy to review any portion of the document before final submission

milestone document content
Milestone Document Content
  • Signed Title Page
  • Table of Contents
  • Executive Summary
  • Introduction
  • Main content
  • References
  • Appendix
  • Index
  • Glossary

Submissions will be on paper – Use a 3 ring binder

discussion question
Discussion Question
  • What actionable things can you do as a project manager to have an effective meeting? (Due Monday – See Drop Box on Angel)