| Autumn
Term
Overview:
During this term you will
be put
into groups which you will work in for the year. You will learn
about
SWENG principles, object-oriented programming, and accounting and
finance in both lectures and
practical exercises. As a group you will construct a QA manual
for
your company.
Lectures:
*
Ross Kirk: Software Engineering Processes
*
Stuart Porter: Fundamentals of Object-Oriented Programming using JAVA
* Tony Ward:
Accounting and Finance
Deliverables:
*
week 10 [Fri] : Draft QA manual to Supervisor. Submit a printed copy to the general office.
Glossary
QA manual: A Quality Assurance
manual that defines
your company's policy and operating procedures.
Staff Roles
Supervisor: During
Week 5 you will be allocated into working groups. Each group has
a
primary supervisor. This person is your first channel of communication
regarding the project. Each group also has a secondary supervisor.
JT: Prof Jon Timmis. SWENG Project
Coordinator.
Chief Customer.
TW: Tony Ward. Customer's external
Financial
backer.
Links
|
Spring
Term
Overview:
You will be given the
actual programming
task, and asked to complete a thorough design by the end of term.
You will also be producing (and working to) a financial statement.
Extra
training will be given in the JAVA environment. Interactions with other
groups occur via agreed specifications and contracts.
Lectures &
Labs:
* [wk1]
Stuart Porter: Intensive JAVA Lab
*
[wk 2] Jon Timmis:Introduction to the task
*
Stuart Porter: JAVA development environment
Deliverables:
*
week 4 [Fri] : Revised QA manual to supervisor (via general office)
*
week 4 [Fri]: Business Plan and QA manual to
TW (copies to JT via general office)
*
week 5: Functional Specification to supervisor
*
week 6[Fri]: PWS agreed.
*
week 7 [Fri]: (am) Tender Presentations - LN/007 to TW, JT
and supervisors.
(pm) Group meetings with TW.
*
week 7: Financial report to TW - submit by email to TW.
*
week 8: Contracts agreed.
*
week 9: Finanical report to TW. Submit by email to TW.
*
week 10: GDS and IDS complete, and copy given to
supervisor as PDF by email. Printed version should be submitted to the general office.
Test & Integration plan complete.
Glossary
Business Plan: The contents of this
document will form the basis of the financial operation of the
company. You will liaise with the Financial Backer based
on this plan.
Functional
Specification: A
written statement of what your product will do. Your supervisor
acts
as a line-manager for the Customer, and should sign the agreed
specification.
Tender Presentation: A 20-minute group
presentation
of your product idea, and your group's QA and design philosophy -
aiming
to convince the chief customer and Financial Backer to support your
company's bid.
PWS: Project-Wide Specification; file
formats
and other information agreed as standard between all groups.
Contract: An agreed exchange of work with
another
group.
GDS: General Design Specification; a
'block overview'
of the main software structure, showing the links between blocks.
IDS: Internal Design Specification; the
functional
structure of the code, its constituent parts, and the outline of the
algorithms
and data required.
|
Summer
Term
Overview:
This is the term when the
bulk
of the programming is done. At the end of term you will present
your
product to the customer and financial backer, and submit a CD-ROM
containing
all your code, documentation and SWENG procedures.
Deliverables:
*
week 5: Interim financial report to TW submit via email.
*
week 8: Financial Summary Report to TW submit via email.
*
week 10[Mon]: Demonstration and sales presentation.
*
week 10[Tue]: Hand-in of DVD to the general office containing the following deliverables:
QA manual & audits
& metrics,
PWS, Functional Specification, GDS, IDS, User Manual,
Contracts, Test
& Integration plan & reports, Financial report, Source
Code,
Minutes of meetings, an example Multimedia Presentation, and an HTML
tour of the product.
Glossary
Sales presentation:
A presentation
of your product (including a demonstration) to the sales team. It
also includes an overview of your company's QA, design, coding &
testing
procedures.
audits: Reviews of
QA procedures
metrics: data
gathered as
part of QA process
User Manual: A
guide to
how to use the product.
Test & Integration
plan:
Testing philosophy and detailed information about how the product
is built.
HTML tour: A
web-style
overview of the key features of the group and the product.
|
