Scribd
Upload
331 views

Software Design m1 CSC - Lab Assignment 1

This document outlines a software design lab assignment to create a banking application using architectural patterns. The application must allow regular bank clients and administrator employees to access accounts. Regular users can view and transfer between their accounts, while administrators can create, update, delete and view client information and accounts. Students must design the application using appropriate architectural patterns, implement and test it, and produce analysis/design documents and source code files.

Uploaded by

Vasy Andrew
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
331 views

Software Design m1 CSC - Lab Assignment 1

This document outlines a software design lab assignment to create a banking application using architectural patterns. The application must allow regular bank clients and administrator employees to access accounts. Regular users can view and transfer between their accounts, while administrators can create, update, delete and view client information and accounts. Students must design the application using appropriate architectural patterns, implement and test it, and produce analysis/design documents and source code files.

Uploaded by

Vasy Andrew
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

UTCN

Computer Science Department


Software Design 2019
Software Design M1 CSC - LAB ASSIGNMENT 1
==================================================================
==
1. Objective
The objective of this assignment is to allow students to become familiar with architectural
patterns.

2. Application Description
Use Swing/C# API to design and implement an application for the clients and employees of a
bank. The application should have two types of users: a regular user which would be a client
of the bank and an administrator user represented by an employee of the bank. Both users
have to provide a username and a password in order to use the application.

The regular user can perform the following operations:


- View all accounts (account information: identification number, type, amount of money,
date of creation).
- Transfer money between accounts.

The administrator user can perform the following operations:


- CRUD on clients information (name, identity card number, personal numerical code,
address, etc.).
- Create/update/delete/view clients' accounts.

3. Application Constraints
The data will be stored in a database. Use the Layers architectural pattern to organize your
application. Use a domain logic pattern (transaction script or domain model) / a data source
hybrid
pattern (table module, active record) and a data source pure pattern (table data gateway, row
data
gateway, data mapper) most suitable for the application.

4. Requirements
- Create the analysis and design document (see the template).
- Implement and test the application.

5. Deliverables
- Analysis and design document.
- Implementation source files.

6. References
Martin Fowler et. al, Patterns of Enterprise Application Architecture, Addison Wesley, 2003
http://java.sun.com/docs/books/tutorial/uiswing/
http://java.sun.com/j2se/1.4.2/docs/api/javax/swing/package-summary.html
http://www.exampledepot.com/egs/?
http://java.sun.com/docs/books/tutorial/jdbc/basics/index.html
http://msdn.microsoft.com/en-us/library/54xbah2z(VS.80).aspx
http://msdn.microsoft.com/en-us/library/e80y5yhx(VS.80).aspx

You might also like