C2002 Software Engineering Term 2 2008 assignment, part 1
Hey all! 
Now I will post the second module assignment in this IADIC assignment posting series, this module is C2002 Software Engineering. This module has quite a lot of technical theory about software engineering. The topics that will be covered in this assignment are software life cycle model, software quality, and software project risk.
The assignment is based on a scenario about development of a CFMS (Cash Flow Management System). We take a role as a freelance software consultant that will help to make decision about the development of this CFMS system.
I will post the scenario and the questions in this post and continue with my answer on the next post.
Here are the scenario and the questions:
I. SCENARIO
Imagine that you are a freelance software consultant, and you have been asked to develop and market a financial software package that can help small trading companies to manage their cash flow.
The initial statement of requirements for the software package is as follows:
Cash Flow Management System (CFMS)
The Cash Flow Management System will be a small and easy to use software that will run on standard Windows based PCs. As most trading companies run a small LAN of PCs, the CFMS software is expected to run on a number of the common network operating systems (e.g, NetWare, Windows NT, etc.).
The system will store details of all the bank accounts held by the company, including name of bank, account name and number, sort code, etc. For each account, all regular payments are held on a file. These include direct debits, giro deductions, bank transfers, and other regular payments. Some of these payments are for fixed amounts, e.g, payment of rent, income tax, property tax, etc. Others like payments to credit card companies, utilities, CPF contributions, etc., will be variable. The periods of payments will also vary (e.g, monthly, quarterly, half-yearly, yearly).
Apart from payments, income received must also be recorded. The user must record the amounts of variable transactions as and when they come in, including dates and amounts of any cheques written.
CFMS will be required to calculate (at any time), the balance left in each account for each day in the coming month. The system should be able to warn the user by showing the date on which the account will become overdrawn, and the amount of the overdraft up to end of the month.
The CFMS system should also have the capability to extract and generate various data into the PCs spreadsheet software to allow the accountants to perform further analysis.
End of Statement of Requirements for CFMS
END OF SCENARIO
II. Questions
(a) State which software life-cycle model (or models) you will apply for the development of the CFMS software. Justify the reasons for your choice and explain each phase in detail. [20 marks]
(b) Discuss how you would go about ensuring the dependability of the CFMS software that is being developed. [10 marks]
(c) Evaluate some of the possible risks to the CFMS software development project and how you would minimize them. [10 marks]
To be continued in the next post….
Do you have any comment on this? maybe you have something to ask me or want to discuss with me about this?Or maybe you are IDIC student and taking this module also?
Feel free to use the comment box below (click here if you cannot see the comment box).
Stay tuned! you can subscribe to my blog’s feed by clicking here so you won’t miss when the new post is published 
pls sir try and post the software engineering term two assignment,your contribution has helped me so much.i will be glad if this assignment is uploaded here on your blog post.we have less than two weeks to submit the assignment.at least your post will be a better guid to help us do the assignment.thanks