CS 330 Software Engineering Project Teams
Project Team 1: Mbark Biometrics (Ross Micheals, NIST)
*System configuration & state visualization for a biometric
application platform*
Despite existing efforts, building modern biometric applications (or
/clients/) that are flexible with respect to changes in sensors,
workflow, configuration, and responsiveness remains both difficult and
costly. The Multimodal Biometric Application Resource Kit, or MBARK
reduces the complexity and costs of implementing such an
application. MBARK is public domain source code that may be leveraged
to develop the next-generation of biometric and personal identity
verification applications
(http://www.itl.nist.gov/iad/894.03/nigos/mbark.html).
Unfortunately, the flexibility of MBARK comes at the cost of
complexity. Although MBARK uses a unified XML format for both
configuration and application state serialization, understanding the
contents of these files currently requires an expert. The purpose of
this project would be to reduce this 'barrier of entry' by developing
two style-sheet transforms (XSLTs) that would transform the
configuration files into (1) HTML and (2) XAML to make it easier for
non-experts to understand the file contents. Such a tool will likely
require first developing a formal XML Schema (XSD) for the files along
with accompanying documentation.
Contact Information:
Ross J. Micheals, PhD
National Institute of Standards and Technology
100 Bureau Drive, Stop 8940
Phone: (301) 975-3234
ross.micheals@nist.gov
Requirements Team
- Andrea Brunner, abrunner@uccs.edu (719)282-4125
- Cody Moss, cmoss@uccs.edu (303)903-6225
- Mark Smith, msmith0@uccs.edu (719)291-5222
- Chris Smith, cdsmith@twu.net (719)473-0826
Comments:
Document Good detail, strong usecases, strong analysis. Initial version has
some soft language, but good SQA follow up. No schedule.
Interview/Process Excellent interview detail and analysis.
Requirements SQA Team
- Laura Yule laura.yule@gmail.com 719-244-4137 (lead)
- Ryan Thomas RyThomas@gmail.com (719)229-8235
- Erik Conser econser@gmail.com (719)930-9722, (719)637-5652, (719)637-6517
- Daniel Ruiz duriz@uccs.edu (719)545-4047
- Chris Flesia Chris.Flesia@gmail.com (719)330-4771
Comments:
No requirements review doc. Okay audit, good comments in document.
okay schedule.
Specification Teams
Same as Requirements
Spec Team SQA
- Daniel Ruiz duriz@uccs.edu (719)545-4047 Lead
- Chris Flesia Chris.Flesia@gmail.com (719)330-4771
- Laura Yule laura.yule@gmail.com 719-244-4137
- Nick Heen nheen@uccs.edu 719)638-5609
- Ryan Freckleton ryan.freckleton@gmail.com 719-287-6349
Design Team
Design SQA Team
Project Team 2: UCCS Routing Forms (Gwen Genaro)
This project will develop an fully electronic distributed replacement
for the campus proposal routing sheets. It will include both the
appropriate forms, a database/store for proposals, both pending and
past, and budget information for each proposal.
Contact:
Gwen Logan Gennaro
Director
Office of Sponsored Programs
University of Colorado at Colorado Springs
1420 Austin Bluffs Parkway
Colorado Springs, CO 80918
Phone: 719.262.3153
Fax: 719.262.3706
Email: ggennaro@uccs.edu
Requirements Team
- Dan Szarkowski - dszarkow@uccs.edu 719-337-5905
- Chris Eberle - eberle1080@gmail.com 719-3527036 -
- Randy Johnson - rjohnso7@uccs.edu 719-201-8348 -
- Von Drake Ramos VRAMOS2@UCCS.EDU (719)574-3763
Comments:
Document Too much "design" in some areas, lacking detailed on interface
requirements issues.
Interview/Process: Needed to track changes in document.
Weak traceability.
No schedule
Requirements SQA Team
Comments:
Needed to track changes in document. Good audit checklist, no
requirements review doc. Weak traceability. No schedule
Specification Teams
Spec Team SQA
- Joseph Mann joedamann17@gmail.com 719-369-4356 (lead)
- Ryan Thomas RyThomas@gmail.com (719)229-8235
- Erik Conser econser@gmail.com (719)930-9722, (719)637-5652, (719)637-6517
- Cayle Stickler ostrosco@nerdshack.com 719-244-1296
Design Team
Design SQA Team
Project 3: Salvador Imaging, Spatial-Temporal Filtering (Tom
Vogelsong)
This project will develop spatio-temporal filters for improving the
operations of Salvador Imaging cameras. The core processing will
(eventually) be done in FPGA, with software simulation and a UI to
allow control and development before reprogramming the FPGA with
particular new parameters. A team of students is already working on
the FPGA implementation, this will formalize the specification and
will also define the simulation software and UI specification.
Contact:
Thomas L. Vogelsong, PhD
Director, Business Development
Salvador Imaging, Inc.
phone: (719)598-6006
fax: (719)598-6556
e-mail: tvogelsong@salvadorimaging.com
web: www.salvadorimaging.com
Requirements Team
- Ryan Freckleton ryan.freckleton@gmail.com 719-287-6349
- Joseph Mann joedamann17@gmail.com 719-369-4356
- Laura Yule laura.yule@gmail.com 719-244-4137
- Cayle Stickler ostrosco@nerdshack.com 719-244-1296
- Daniel Ruiz duriz@uccs.edu (719)545-4047
Comments:
Document Good overall. Lacking a bit in usage.
Interview/Process Weak interview many pauses not sufficient
questions/reflectors. Followup not documented.
Good schedule. Good tracibility.
RequirementsSQA Team
- Andrea Brunner, abrunner@uccs.edu (719)282-4125 Team Lead
- Mark Smith, msmith0@uccs.edu (719)291-5222
- Randy Johnson - rjohnso7@uccs.edu 719-201-8348 -
- Von Drake Ramos VRAMOS2@UCCS.EDU (719)574-3763
Comments:
Okay audit good comments in doc. No clear tracability of who did what (all
marked AB). No requirements review doc. No schedule.
Specification Teams
Combined 3 & 5
Spec Team SQA
- Chris Eberle - eberle1080@gmail.com 719-3527036 - Team Lead
- Andrea Brunner, abrunner@uccs.edu (719)282-4125
- Mark Smith, msmith0@uccs.edu (719)291-5222
- Randy Johnson - rjohnso7@uccs.edu 719-201-8348 -
- Von Drake Ramos VRAMOS2@UCCS.EDU (719)574-3763
- Cody Moss, cmoss@uccs.edu (303)903-6225
- Chris Smith, cdsmith@twu.net (719)473-0826
- Dan Szarkowski - dszarkow@uccs.edu 719-337-5905
Design Team
Design SQA Team
Project Team 4: Salvador Imaging, Color Camera (Tom Vogelsong)
This project will develop new color-processing software/filters for
improving the operations of Salvador Imaging cameras. The core
processing will (eventually) be done in FPGA, with software simulation
and a UI to allow control and development before reprogramming the
FPGA with particular new parameters. A team of students is already
working on the FPGA implementation, this will formalize the
specification and will also define the simulation software and UI
specification.
Contact:
Thomas L. Vogelsong, PhD
Director, Business Development
Salvador Imaging, Inc.
phone: (719)598-6006
fax: (719)598-6556
e-mail: tvogelsong@salvadorimaging.com
web: www.salvadorimaging.com
Requirements Team
- Ryan Thomas RyThomas@gmail.com (719)229-8235
- Chris Flesia Chris.Flesia@gmail.com (719)330-4771
- Erik Conser econser@gmail.com (719)930-9722, (719)637-5652, (719)637-6517
- Nick Heen nheen@uccs.edu 719)638-5609
Comments:
Document No use-cases. Lacking detail on usage processes or integration.
Interviews/process: (no documents/notes provided, even after SQA
team prompted for them). No followup interview/questions either
No schedule, very weak traceability.
SQA Team
- Cody Moss, cmoss@uccs.edu (303)903-6225 Team Lead
- Chris Smith, cdsmith@twu.net (719)473-0826
- Dan Szarkowski - dszarkow@uccs.edu 719-337-5905
- Chris Eberle - eberle1080@gmail.com 719-3527036 -
Comments: No requirements review doc. Okay audit, good comments in
document. No schedule
Specification Teams
Spec Team SQA
Design Team
Design SQA Team
Requirement's Team Assignments
By 2/21/2006 you are to turn in (eletronically)
- A schedule for your requirements team efforts, who is doing what, when and where.
- Scheduled contact with client and mode (phone/personal visit)
- A list of interview questions the questions you plan to ask,
There is not a separate grade for this, its part of your overall
Requirement team package. You are to turn in, electronically,
By 2/23/2006 (11:59pm) you are to turn in (electronically)
- A revised schedule
- Your notes from your first client meeting,
- and some interpretation/summary what you learned, from those questions
- if possible, some suggested questions for you follow up meeting.
-
Requirement's Team SRS Doc Assignment (Due 3/02/07)
Your full, complete Requirements (SRS) document, should be checked
into CVS for your team's repository. Its naming should be obvious.
You should also check in:
- Your notes from your client meeting(s),
- The prepared questions for each interview
- the schedule, as planned and as executed including approximate listings of
who did what and how many hours were spent on each task.
- A "Readme.txt" that described each file.
If something goes wrong and your team is having real problems with
CVS, you can email me the documents to ensure there are no late
penalties.
The SRS document is the "artifact", and should be presented
professionally. The remainder is internal materials to be used by the
SQA group, and may be scanned hand-written notes and such.
Each team member should individually email Dr. Boult their "team
assessment" where you comparatively state perceived differences from
the team official schedule, and then provide your assessment of the
appropriate splits of the overall team grade. As in all
self-assessments, explicitly state your strengths and weakness and how
you would do better next time.
Requirement Initial Draft SQA Team SRS Doc Assignment (Due 3/15/07, 8am )
Your analysis of your assigned SRS, and accompanying documents, should be checked
into CVS for that teams's repository. You should be completing an
SQA-srs-audit document, as well as adding detailed comments/corrections into
the SRS document itself. Who made what comments/changes should, of course,
be traceable.
Each SQA team member should individually email Dr. Boult their "team
assessment" where you comparatively state perceived differences from
the team official schedule, and then provide your assessment of the
appropriate splits of the overall team grade.
Requirement's Team SRS Final Document Assignment (Presentation in Class 3/23/07, Documents Due 3/23/07 5:00pm)
Your team will give a presentation, 5 mins per team members, that is a
walkthrough of your requirements document. Each team member will be
graded, individually, on clarity of presentation, quality of
presentation, good eye contact with the audience and overall technical
professionalism (but no need to dress up).
Class will also provide feedback on the requirements documents and
may challenge assumptions and/or provide other critiques (and remember
class participation Each class member will also fill out a SRS
Walkthrough doc based on your team's presentation, so you might
want to look at it as you prepare the walkthrough.
Your full, complete Requirements (SRS) document, addressing all SQA issues, should be checked
into CVS for your team's repository. Its naming should be obvious.
You should also check in:
- Your notes from your second client meeting(s),
- The prepared questions for each interview
- the schedule, as planned and as executed including approximate listings of
who did what and how many hours were spent on each task.
The SRS document is the "artifact", and should be presented
professionally. The remainder is internal materials to be used by the
SQA group, and may be scanned hand-written notes and such. The SRS
Document, after any final changes after presentation, will be emailed
to your clients for their analysis.
Each team member should individually email Dr. Boult their "team assessment"
where you comparatively state perceived differences from the team official
schedule, your strengths and weakness, how to improve and then provide your
assessment of the appropriate splits of the overall team grade.
Maintenance Team, initial assignment
Download, install and get running OpenCV on at least 2 different
OS/platforms. The don't need to be installed in special locations
(e.g. /usr/local) and can be entirely in your space.
Modify one of the sample applications in a meaningful but simple way and
compile and run it on both platforms and provide output to show both the
compile and the operation of your program.
maintenance Team 1
- Erik Conser econser@gmail.com (719)930-9722, Team Lead
- Andrea Brunner, abrunner@uccs.edu (719)282-4125
- Chris Flesia Chris.Flesia@gmail.com (719)330-4771
- Chris Eberle - eberle1080@gmail.com 719-3527036 -
Maintenance Team 2
- Randy Johnson - rjohnso7@uccs.edu 719-201-8348 Team Lead
- Dan Szarkowski - dszarkow@uccs.edu 719-337-5905
- Cody Moss, cmoss@uccs.edu (303)903-6225
- Chris Smith, cdsmith@twu.net (719)473-0826
Maintenance Team 3
- Cayle Stickler ostrosco@nerdshack.com 719-244-1296 Team Lead
- Ryan Freckleton ryan.freckleton@gmail.com 719-287-6349
- Mark Smith, msmith0@uccs.edu (719)291-5222
- Von Drake Ramos VRAMOS2@UCCS.EDU (719)574-3763
Maintenance Team 4
- Joseph Mann joedamann17@gmail.com 719-369-4356
- Laura Yule laura.yule@gmail.com 719-244-4137
- Nick Heen nheen@uccs.edu 719)638-5609
- Daniel Ruiz duriz@uccs.edu (719)545-4047 Team Lead
Maintenance Team 5
(a team of one)
Ryan Thomas RyThomas@gmail.com (719)229-8235 (differential assignment.. since knows openCV)
Install openCV to use openMP and the intel compiler and IPP and do 2 benchmarks of
Face Training and detection performance to compare standard openCV with the
parallel one.
Maintenance Team Final Assignment (Due 4/30/07)
Using a previously identified bug (in the bug system) or a self-identified
bug approved by the instructor, develop a test program to exercise the bug,
find and fix the bug, and show it passes your test program on both
platforms. Submit bug report via formal bug tracking system.
Specification/Design Team initial Assignment (Due 4/23/07)
Develop team schedule. Check into cvs. Update after completing stage.
Review your assigned SRS and other supporting document, enhance the SRS to
have usage scenarios, Sequence diagrams or other semi-formal high-level
interface/usage specification. Each team member should lead one "diagram"
effort. In the documentation discuss why particular specification/design
choices are being made. Determine 2 aspects of the project that would
benefit from a rapid prototype, e.g. because of their risk, and discuss them,
and the motivation, in a separate document. Check all into CVS.
Begin prototyping key elements identified.
Specification/Design SQA (Due 4/28/07)
Review formal specifications from Specification/Design Team.
Update/comment in/on their documents and drawings based on the SRS (and more
docs if needed).
Specification/Design Team Final Assignment (Due 5/8/07, 8am)
Critiqute team schedule. Check into cvs. Update after completing
stage. Complete prototyping key elements analysis and develop a
document/report. Develop architectural and detailed design document
for project. Your desgin documents should expicitly related back to
the requirements document (numbers and such), clearly stating and
"corrections" or fixed required to that document. Check all into CVS.
In your final self-assessment you are to address how "self-learning"
(a.k.a. life-long learning) impacted your ability effectively deliver
on this assignment and in this course overall. Finally in our
self-assessment relate your experience in this course to the expected
IEEE code of ethics and how/where you used social or ethical
considerations in your requirements/sepcification/design.