Académique Documents
Professionnel Documents
Culture Documents
2.
3.
4.
Name of Course
Project II
Course Code
BACS3413
Name(s) of academic staff
All staffs with at least Master in Science (or relevant) qualifications
Rationale for the inclusion of the course in the programme
The students are required to continue developing a working system or prototype system (if system
is a complex system) following their system planning and design in the previous semester. They
should use appropriate software development tools such as programming languages, CASE tools,
database servers, report generators, debugging tools, etc. during the process of software
development. Software testing has to be performed to ensure accuracy of the system. For
research based project, possible proof of concepts testing is to be conducted to confirm the
feasibility of proposed solutions.
Course Objectives
Enable the students to apply knowledge and skills in designing software test plan or
experiment plan
Engage students in software, system or project development in accordance to the user
and system requirements, and system design
Enable the students to learn and apply thesis or report writing skills
5.
7.
8.
9.
Total SLT
113
120
Learning outcomes
Upon completion of the course, students should be able to:
CLO 1: Use appropriate software development tools to develop a working or prototype
system that closely meets the proposed system requirements and design. (C5, P4,
CTPS, LL)
CLO 2: Conduct software testing using various strategies or proof of concept testing using
CLO 3:
10.
11.
well- organized and proper test cases. (C5, A3, P4, CTPS, CS)
Produce a report that documents the software development life cycle, algorithms,
and evaluation of the project management issues and other issues for discussion
(C6, A3, P4, CTPS, KK, LL)
Transferable Skills:
Skills and how they are developed and assessed, Project and practical experience and Internship
Transferable Skills
Analyse problems and find
appropriate solutions based
on rationale and objective
reasoning
Assessment
Assessed through
progressive evaluation
Assessed through
progressive evaluation
Assessed through
progressive evaluation
Developed through
presentation and report writing
Assessed through
progressive evaluation
Assessed through
progressive evaluation and
documentation
Teaching-learning strategy
Group Discussion
Fact Finding
Literature Review
Requirement gathering and analysis
System Analysis
System Design
Independent Reading
Programming or application of technical skills
Assessment strategy
Continuous progression evaluation by project supervisor
12.
Synopsis
This course provides opportunity to the students to apply their programming skills to develop
software prototypes that closely meet the system requirements and system designs that have
been done in AACS3403 Project I from the previous semester. They may apply the knowledge of
various fields, such as database, Web technology and networking technology, and use
appropriate software development tools to produce a working or prototype system. Software
testing should also be performed to ensure the accuracy and reliability of the system. For
research based project, possible proof of concepts testing is to be conducted to confirm the
feasibility of proposed solutions. Lastly, complete project documentation must be produced.
13.
Mode of Delivery
Project Supervision
14.
Coursework (100%)
Students will be evaluated progressively based on the following project activities:
Software Testing Plan (10%)
System / prototype (60%)
Final Documentation Write-Up (25%)
Project Management (5%)
15.
16.
Course
Programme Education Objectives
Learning
PO1
PO2
PO3
PO4
Outcomes
CLO1
CLO2
CLO3
Mapping of the course to the Programme Learning Outcomes
17.
Course
Programme Learning Outcomes
Learning
PLO1 PLO2 PLO3 PLO4 PLO5 PLO6 PLO7 PLO8 PLO9
Outcomes
CLO1
CLO2
CLO3
Content outline of the course and the SLT per topic
Week
Topic
Student Learning Time (SLT)
L
T
P
O
Total Guided and
Independent
Learning
2
55
1-4
System/prototype development
1
16
5
Software Testing
18.
6-7
Preview and Assessment
4
22
Final Documentation
20
Total
0
0
0
7
113
Total SLT
120
Subject Credit
3
Main references supporting the course
1. Kothari, C.R. 2012, Research Methodology: Methods and Techniques, 2ndedn, New Age
International.
2. Marder, M.P., 2011, Research Methods for Science, Cambridge University Press .
3. Sommerville, I. 2011. Software Engineering. 9hedn. Addision-Wesley.
4. Pressman, R. S. and Maxim, B. 2014. Software Engineering - A Practitioners Approach.
8thedn. McGraw-Hill.
Additional references supporting the course
1. Dennis, A., Wixom, B. H. and Tegarden, D. 2015. Systems Analysis and Design with UML: an
Object-Oriented Approach. 5th edn. John Wiley.
2. Shelly, G. B. and Rosenblatt, H. J. 2012. Analysis and Design for Systems. 9thedn. Course
Technology/Cengage Learning.
3. Hoffer, J. A., George, J. F. and Valacich, J. S. 2011. Modern Systems Analysis and Design.
4. 6thedn. Pearson/Prentice Hall.
5. Creswell J. W. 2013. Research Design: Qualitative, Quantitative, and Mixed Methods
Approaches, 4th edn. SAGE Publications.
6. Bennett, S., McRobb, S. and Farmer, R. 2010. Object-Oriented Systems Analysis and Design
Using UML. 4th edn. McGraw-Hill.
Produce a test plan that utilizes various software testing strategies and
methods
Present the software prototype to the supervisor and moderator(s). The
assessment will be done based on multiple perspectives, such as
conformity of the coding with the design, user interface design,
programming skills, degree of completion, and presentation skill.
Each student must provide:
- A complete documentation, including the updated design
diagrams
- Evaluation of the system coding on how it meets the system
design.
- Evaluation of the project management
- Discussion and future improvement