Software Engineering Course – CSIS 330  

A Course Project Submitted to
Department of Computing
College of Engineering and Applied Sciences
American University of Kuwait
 In Partial Fulfilment of the Requirements for the
Software Engineering Course – CSIS 330
 
 
Project Title
 
 
By
Student name, ID
Student name, ID
Student name, ID
Student name, ID
Student name, ID
Team size Î [3,5]
 
Project Advisor
Any person with relevant expertise to your project 
 
 
Course Instructor
Dr. Aaron Rasheed Rababaah
 
 
Date
Spring 2021
 
 
 
 
TABLE OF CONTENTS
 
 
LIST OF TABLES
 
 
LIST OF FIGURES
 
 
ABSTRACT
 CHAPTER I

  1. INTRODUCTION
    • Background: Situation before your system
      • State of the domain the system is intended to serve
      • Gaps/problems in the domain that need to be addressed by your system
      • Motivations to address these problems
      • How your system going to address these problems

 

  • System Overview: Summary of the entire system
    • Goals
    • Brief description of the design: context, architecture, users etc.
    • Brief description of implementation technology
    • The intended users

 

  • Document Conventions: Terms definitions/Glossary
    • Acronyms
    • Abbreviations
    • Symbols, etc.

 

  • Intended Readership: The target audience/Stakeholders
    • Project managers, customers, end users, customer engineers, customer managers, developers, etc.

 

  • Product Scope: summary of functional/non-functional requirements
    • Brief narrative of the functional requirements
    • Brief narrative of the non-functional requirements

 

  • Team Members Workload Allocation (By chapter)
No. Lead team member 1 2 3 4 5 6 7 8 9 10
7% 7% 20% 25% 15% 10% 7% 5% 2% 2%
1 Khalid X X             X X
2 Fatimah           X X      
3 Saif       X            
4 Lulwah     X              
5 Khalifah         X     X    

 
Notes on teamwork:

  1. Tasks are distributed among team members. See an example in the table above. Each member must handle at least (100%/team size) with -5% tolerance.
  2. Every team member is required to contribute reasonably and fairly to all project tasks.
  3. Every team member is responsible to know about the entire project.
  4. Every team member should lead the efforts to complete his/her allocated work of the project.
  5. During presentation, each member will be asked questions regarding the different development activities.
  6. During demonstration, each member will be asked questions regarding how the system works.
  7. Every team member is required to participate in presentation and demonstration.
  8. Each team will present then demonstrate in the same session.
  9. Teams will take turns for presentations according to their assigned team# given at the time of their proposal.
  10. There will be two anonymous peer-review at the mid and end of the project.

 
 
CHAPTER II

  1. SOFTWARE REQUIREMENTS SPECIFICATION – SRS
    • Feasibility Study
    • User Requirements
    • System Requirements
    • Non-Functional Requirements – NFR
    • Functional Requirements Specifications – FRS (use standard template)
    • Context Model
    • Use Cases
    • Use Cases specifications (use standard template)
    • Preliminary System Architecture
    • Requirements Traceability Matrix – RTM

 
CHAPTER III

  1. SYSTEM DESIGN
    • Sequence Diagrams
    • Data Flow Model
    • Architectural Pattern Selection & Final Architectural Model
    • Activity/Process Model
    • Finite State Machine (if Applicable)
    • Component/Unit design
    • Class Structure Diagram
    • Prototype

 
 
CHAPTER IV

  1. SYSTEM IMPLEMENTATION
    • Make, Buy or Lease Analysis: For each component of the system run critical analysis to make, buy or lease decisions. Consider these factors:
      • Intellectual property
      • Privacy
      • Security
      • Reliable expertise
      • Reliable capacity
      • Feasibility
    • Software Reuse: For each component specify the reuse level as:
      • Abstract level
      • Object level
      • Component level
      • System level

You may present this section using a table as below:

No Component Name Subsystem Decision License Justification Reuse Level Ref. Date
1 Database Server Buy GPL Available for free – open source System Meeting# SI-017 JUL.11.2018
2 Medical analysis Process logic Make N/A Own idea, intellectual property Abstract CEO – MEMO# PROD-009 JUN.17.2018
               

 

  • Coding
    • Screenshot of the project explorer (file system)
    • For each class in the project screenshot the top part of its source file including all required package, libraries, super classes and interfaces. e.g. below:

 
 

  • Configuration Management
    • A common scheme is used which consists of four fields:

Version = phase.major.minor.patch
Phase:
0 for alpha (status): within development team
1 for beta (status): released to testing team
2 for release candidate: potential users and early adapters
3 for (final) release: actual end users
Examples:
V0.1.0.0: alpha, major-1, minor-0, patch-0.
V1.0.1.3: beta, major-0, minor-1, patch-3
V3.1.0.5: final release, major-1, minor-0, patch-3
 
System versions could be presented as a table:

# Change/ Problem Request Assigned
To
Source Comp Version Subsys Old Sys Version New Sys Version Date
1 Replace database comp Ahmad – ID# Customer: rep. Ali – ID# Data
base
5.7.23 Server V0.1.0.0 V0.1.1.0 10.03.2019
2 Customer feedback does not get recorded Omar – ID# Validation test#: V105 Client main page 1.0 Client app V0.1.0.0 V0.1.1.0 11.03.2019
3 Team#7              
  • Host Target Specification: Detailed specifications for target platform requirements including:
    • Hardware: CPU, RAM, I/O devices, networking, etc.
    • Software: OS, web, database, security, libraries, etc.
    • IDE/Compilers: if open source
    • Testing tools

 

  • Deployment/Physical Diagram

 
CHAPTER V

  1. VERIFICATION AND VALIDATION – V&V

Describe how the system was verified and validated throughout the development process. For each of the following elements in 5.1 – 5.3, state what V&V activities were applied.
 

  • Development Testing
    • System Inspection
      • SRS
      • Architecture
      • Design Models
      • Code

 

  • System Testing
    • Development Testing
    • Unit (method)
    • Component (class)
    • Subsystem (layer)
    • System (the entire system)

 

  • Release Testing
    • For this part, split team into two groups, development and testing.
    • Black box and white box testing
    • Identify operational profile
    • Performance testing
    • Use-case/sequence-diagram based testing
    • Requirements-based testing

 

  • User Testing
    • Alpha
    • Beta
    • Acceptance

 
 
CHAPTER VI

  1. SYSTEM EVOLUTION
    • Anticipated System Evolution
No Change Affected Comps Proposed Solution Cost Range
1 GUI Client app Redesign GUI KD500-2000
2 Database Server Replace database with more secure one KD2000-5000
3 Add biometric authentication Client app Add a new class to handle the new hardware. All SE docs need to reflect the change. KD3000-10000
4  …      

 

  • Anticipated System Transitions till Phase-out
    • Prediction of system quality and value for long term. Present data using a table and a column chart.
  • Justify your predictions

CHAPTER VII

  1. SYSTEM PLANNING AND MANAGEMENT
    • Milestones and Deliverables Table
    • Gantt Chart
    • Staff Allocation Chart
    • Activity Network
    • CoCoMo based Costing
    • Risks Identification
    • Risks Assessment Matrix – RAM
    • Root-Cause/Fishbone – Ishiwaka Diagram

 
CHAPTER VIII

  1. CONCLUSIONS
    • Seven Design Smells

How does your system stand with regard to:

  • Rigidity
  • Fragility
  • Immobility
  • Viscosity
  • Needless Complexity
  • Need Repetition
  • Opacity

 

  • System Strengths and Weaknesses – SWOT
  • Future Work and Recommendations

 
 
CHAPTER IX

  1. APPENDICES

Any submental material that is too detailed to be included in the respective sections should be appended here and properly referenced in the report. Examples of appendices: source code (don’t include it for this report), data, files, third party large tables or diagrams, surveys, questionnaires, mathematical proofs or derivations, etc. Any material that is not critical to the section but for convenience, we can add it at the end of the repot in the appendices.

  • Appendix 1
  • Appendix 2

 CHAPTER X

  1. REFERENCES

[01]      Rababaah, Aaron R. (2021), Class Notes and Supplements, Software Engineering CSIS 330, Department of Computing, College of Engineering and Applied Sciences, American University of Kuwait, Spring-2021.
[02]      …
[03]      …
Order Now

Calculate a fair price for your paper

Such a cheap price for your free time and healthy sleep

1650 words
-
-
Place an order within a couple of minutes.
Get guaranteed assistance and 100% confidentiality.
Total price: $78
WeCreativez WhatsApp Support
Our customer support team is here to answer your questions. Ask us anything!
👋 Hi, how can I help?