IT 446-447 Senior Projects (Capstone)

1
IT 446-447 Senior Projects (Capstone)

• Where the academic rubber meets the system
  development road.

2
Things to Remember

• What you get out of this class will depend almost
  entirely on what you put into it.
• You will be graded mostly on the artifacts you
  produce as a team.
• Your individual grade will be a function of your
  Team Grade, coaches evaluation and your Team
  members evaluations of performance
• You are responsible to ask for help when you need
  it, in this class and in your future profession.
  Your boss wont try to read your mind.

3
Context or Domains

• University (BYU specifically)
• Accreditation bodies
• Education models
• IT
• Academic
• Industry Umbrella
• Business
• Business Models
• Pays for everything
• Personal
• Seniors ready to graduate
• Looking for a job?

4
Introduction Terminology

• Business
• Model
• Domain
• Project
• Product
• Development
• System

• Team
• Conflict
• Success
• Failure
• Other ambiguous terms.

5
Business Models

• http//en.wikipedia.org/wiki/Business_model
• IT is an Accelerator (Jim Collins) It does not
  automatically produce profits.
• Business system development model
  Waterfallhttp//en.wikipedia.org/wiki/Waterfall_m
  odel
• See also spiral, iterative and agile development
  models

6
Project Lifecycle models

• http//en.wikipedia.org/wiki/Project_lifecycle
• Big deal in Software Engineering
• Applies to any system of which software is a
  component! And almost any other development
  project.
• Remember You will work in the model your
  manager wants you to. Be aware of the pitfalls
  of the waterfall!

7
Learning/Educational models

• ABET (accredits engineering technology
  including Computer Science, Computer Engineering
  and IT)
• Objective What you can do 5 years after
  graduation.
• Outcome What you can do at the end of an
  educational experience.

8
IT 446 Learning Outcomes

• Conceive and present project ideas.
• Develop a professional quality resume
• Describe the (Tuckman teamwork model Forming
  Storming, Norming, Performing). (3)
• Participate as a responsible member of a team in
  project design and regular project review
  meetings with a coach
• Set up a Project Management system using.
  Pert/Gantt charts, resource scheduling etc. (2)
• Manage change in projects using project tools(1)
• Estimate Project requirements (initial design).
  Produce accurate estimates of materials,
  resources and time needed for its completion.
• Use professional resources to acquire materials
  and resources for projects from suppliers. (1)
• Find and use appropriate research and development
  resources. Evaluate information source
  reliability.
• Describe intellectual property protections and
  how they apply to IT projects
• Understand and apply principles of creativity.
  Expansion and restriction. (lateral thinking and
  analysis) (2)
• Develop performance specifications for the
  project
• Develop test specifications for the project.
• Integrate parts of the project into a cohesive
  whole.
• Complete the design of the final project (in the
  form of a detailed feasibility study) (3)
• Demonstrate presentation skills in presenting
  projects in a formal setting with the goal of
  achieving support (funding). (3)
• Describe and practice skills and methods of
  life-long learning (1)

9
Ambiguity

• The meaning of a term is a function of context
  (or domain model).
• When you are dealing with multiple domains (which
  is most often the case) make sure you lock down
  the meaning of the terms!
• Every project this semester will create a
  language specific to the project. In your
  presentations, make sure to reveal the meaning of
  project specific terms.
• TLAs are obviously part of the private language,
  Other terms are not.
• Project, System, Development, Teamwork, and
  Success are some of the most ambiguous terms in
  the English Language.