INFO 424 Week 11 INFO 424 Team Project Practicum Week 1 Glenn Booker

INFO 424 Overview This course is to get you ready for the senior design sequence, INFO , and develop team project skills It gives you a chance to understand the process and the document templates It builds on the foundation courses you’ve completed over the last couple of years INFO 424 Week 12

The Path to Senior Design INFO 424 Week 13 Concept from Prof. Hislop Programming HCI Analysis & Design Senior Design Project Mgmt Networking, Server? Database This course!

Your Role Your role is to treat your work in this class as seriously as your work for a co-op or other ‘real’ employer Appropriate use of professional tone, and quality work INFO 424 Week 14

My Role My role for this course is more of a mentor and guide than lecturer –Ok, there are lecture materials, but mostly to outline the process we’re using, and remind you what you learned in INFO 200, 355, 420, etc. –Some class periods may become review time for your draft work INFO 424 Week 15

Our Development Approach We’re following a cyclical development approach –Each cycle includes requirements, design, and implementation work –The first cycle focuses more on req’ts and design; later cycles more on implementation This course will follow one cycle –INFO will have three cycles INFO 424 Week 16

Our Development Approach This approach provides a balance between a traditional waterfall life cycle, and faster RUP or Agile methods, which typically don’t exceed four weeks per iteration or time box INFO 424 Week 17

Copyright by Gregory W. Hislop 8 Cycle Phases and Products PhaseDeliverable LaunchLaunch Report RequirementsRequirements Spec (SRS) Test Specifications DesignDesign Spec (SDS) PrototypeImplementation Customer Documentation Post MortemLaunch Report

Templates All of the documents have templates –Much kinder than giving no guidance –Use the templates! –Don’t delete sections If it’s truly irrelevant, add a sentence to indicate it’s not applicable to your system Then think again and make sure it really is –Each template also has rubrics, to provide a consistent basis for grading INFO 424 Week 19

IEEE Standards IEEE Standards are used for the basis of two templates –IEEE 830 is the basis for the software requirements specification (SRS) –IEEE 1016 is the basis for the software design specification (SDS) Why? These standards capture industry best practices INFO 424 Week 110

IEEE Standards There are instructions on my web site for downloading these standards –BTW, you may wish to download more of these standards –They’re free while you’re here, very pricey otherwise –For example, user documentation isn’t prepared this term, but you could use that standard to help next term INFO 424 Week 111

Copyright by Gregory W. Hislop 12 Project Portfolio Hardcopy and softcopy required –Both due on deadline date Softcopy –Post to the course site Communications…Group Pages… … Group Discussion Board…Team Products –Softcopy file names Cycle-Team-Document Example: C1-Blue-SRS

Copyright by Gregory W. Hislop 13 Project Portfolio Hardcopy - Build a project portfolio –Formal record of the project work –Primary vehicle for feedback from me –Submit in class or my 3 rd floor mailbox Submit in a folder or accordion file –Three ring binders do not work well –Contents are cumulative All graded products All drafts reviewed by me –Re-submit with each new document –Maintain across the term

Copyright by Gregory W. Hislop 14 Project Drafts Submit drafts of document sections to the online course area –Initial writing –Significant re-writes and editing –See syllabus for instructions on location and naming Purpose is to provide a record of individual work –Items do not count as team deliverables –I will not read most of these items

Copyright by Gregory W. Hislop 15 Project Implementation Submit the full implementation to the course site –Discuss format if needed End of term CD –Include all documents (SRS, SDS, etc.) –Include all implementation work –Package the material as you would to let someone else install the product

Course evaluation The work done your team is the basis for 70% of your course grade The rest is individual contribution, measured by –Peer evaluation –My observations –Your team’s project portfolio INFO 424 Week 116

Team Selection Teams for this course will consist of 3-5 people, selected by you during the first class –Each team will get a Group communication area in Blackboard You may choose to keep the same teams and project for INFO , but it isn't required INFO 424 Week 117

Project topic Your team will choose the subject of your project (see handout) Two major types of options –Your team’s idea –Support a faculty research project Teams may work on the same project Instructor approval of topic is required INFO 424 Week 118

Project topic Projects must include some significant software development aspect They may include hardware They can be real or fictitious Keep the cycle structure in mind –An early need will be to plan what will be implemented in each cycle INFO 424 Week 119

Project topic Implementation of part of the system is required Some projects have predefined development environments Some allow you to choose the development environment INFO 424 Week 120