T2 System - ‘B’ Level Synopsis



<PICTURE / LOGO of your project, if ANY>

< Project Name>

Team:

Architect and Developer        : <your name> < team name >

Guide Name                        : < guide name>

 

This page is intentionally left blank.

 Table of Contents:

1 Introduction        4

1.1 Problem Statement:        4

1.1.1 Background:        4

1.1.2 Problem:        4

1.2 Why is the particular topic chosen?        5

1.3 Contribution        5

1.4 Objective & Scope        6

1.4.1 Objective        6

1.4.2 Scope        6

1.5 Statement to Declare        8

2 Methodology        9

2.1 Architecture        9

2.1.1 Benefits of N-Tier Architecture        9

2.1.2 Benefits of SOA        10

2.2 Modules        11

2.3 Hardware & Software used        12

2.3.1 Hardware        12

2.3.2 Software        12

2.4 Testing Technologies used        13

2.4.1 Black box        13

2.4.2 White box        13

Suggestion/ Notes        14

 1 Introduction

1.1 Problem Statement:

1.1.1 Background:

 <background on why you have choose to do>

1.1.2 Problem:

<problem>

Throughout the process, the following problem has been identify:

1.

2.

3.

 

1.2 Why is the particular topic chosen?

The main reason of choosing this project is that the business needs the solution to automate this process as discussed in our problem statement.

If this project has successfully implemented, it would definitely help end-users by saving time, error free operations, less manpower required and support to the environment by having paper less process.

1.3 Contribution

  1. Contributing to the environment through reducing paper work

  1.  

  1. Contributing to the contractor by managing the system from centralized system.

  1. Contributing to the developers by adopting a latest technology such as Silverlight, .Net 3.5, LINQ.

 1.4 Objective & Scope

1.4.1 Objective

<objective?>

1.4.2 Scope

 Following is the use case diagram for the system that covers all primary actions that different actors can do.

<define the use case , if any>

 Actors and their main responsibilities:

<list of actors involved>

1.5 Statement to Declare

<ONLY if you are not submitting your CODE>

This project belongs to the company where I’m working and because of the Employee Non Discloser Agreement (NDA) I’m not allowed to share any material that goes against the agreement. Hence, the final project report can include in-depth documentation about various modules, technique, screen shots, and pseudo code used that may vary as compare to the actual software, but functionality would remain as it is.

 2 Methodology

2.1 Architecture

Every system got its own architecture that defines how distinct components are running in a separate runtime environments.  

 

<define the architecture>

2.1.1 Benefits of N-Tier Architecture

There are many business benefits to N-Tier Architecture. For example, a small business can begin running all tiers on a single machine. As traffic and business increases, each tier can be expanded and moved to own machine and then clustered. This is just one example of how N-Tier Architecture improves scalability and supports cost-efficient application building.

2.1.2 Benefits of SOA

SOA offer the following advantages over traditional approaches to distributed computing:

 2.2 Modules

<make a picture of your modules>

<your system> consist of four modules:

  1. Mobile Application:
  2. 2. 4.  2.3 Hardware & Software used

2.3.1 Hardware

2.3.2 Software

 2.4 Testing Technologies used

 

 

2.4.1 Black box

 

Black box Testing is also referred to as functional testing. It focuses on testing the internal machinations of whatever is being tested, in our case, a client or server program.

Black box testing is being handle by the dedicated team responsible for it.

Technique used by Test Team:

Technique used by developers:

2.4.2 White box

White box testing is also sometimes referred to as glass box testing. It is a form of structural testing that is also called clear box testing or open box testing. As expected, it is the opposite of black box testing. It focuses on the internal workings of the program and uses programming code to examine outputs.


Technique used by developers:

 Suggestion/ Notes

-- End --


14/14

        

Submitted by: <Your name>                 Reg. No: <your doe registration number>