<Project Name>

Team:
Architect and Developer : < Your name probably >
Guide Name : < Of course not your name ;)>
 ‘B’ Level Synopsis

This page is intentionally left blank.

2/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

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....................................................................................................................................9
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

3/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

1 Introduction

1.1 Problem Statement:

1.1.1 Background:

1.1.2 Problem:

Throughout the process, the following problem has been identify:

1. Point one
2. Point two
3. Point point point 

4/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

1.2 Why is the particular topic

chosen?
The main reason of choosing this project is that the …

1.3 Contribution
1. …

5/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

1.4 Objective & Scope

1.4.1 Objective

This project aims at developing …

1.4.2 Scope

 To get girls.

6/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

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

7/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

Actors and their main responsibilities:

1.5 Statement to Declare

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. Well you might want to remove this, if you are submitting your
code.

8/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

2 Methodology

2.1 Architecture
The architecture diagram

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.

 Readable and reusable

 Robust

 Ease

2.1.2 Benefits of SOA

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

 They offer business services across the platforms

 They provide location independence

 Services need not be at a particular system or particular network

 Completely loosely coupled approach

9/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

 Authentication and authorization support at every level

 The search and connectivity to other services is dynamic

 Different presentation layer can use the same Business layer.

10/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

2.2 Modules
1.

11/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

2.3 Hardware & Software used

2.3.1 Hardware

 Minimum: 1.6 GHz CPU, 384 MB RAM, 1024x768 display, 5400 RPM hard disk

 Recommended: 2.2 GHz or higher CPU, 1024 MB or more RAM, 1280x1024 display, 7200
RPM or higher hard disk.

 On Windows Vista: 2.4 GHz CPU, 768 MB RAM

2.3.2 Software

 Microsoft Windows 2003 or later operating system

 Internet Explorer 7 or later

 Visual Studio 2008 Professional Edition; .Net 3.5 framework.

 Microsoft Expression studio

 Silverlight runtime & Silverlight SDK

 Silverlight Unit Testing SDK

 MS SQL Server 2005 or later

 IIS 6.0 or later

12/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

2.4 Testing Technologies used

Since client-server technology relies so heavily on application software and networking, testing is an
important part of technology and product development. There are two distinct approaches when
creating software tests. There is black box testing and white or glass box testing.

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:

 Test Team is responsible to do performance, integration, and system testing, through unit
testing; writing test cases and execute the same for the conclusion.

Technique used by developers:

 Using Unit Test project on server side components

 Using Silverlight Unit Test project on client side components

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:

 The white box testing is being handled through Peer review; following agile software
development.

13/14

Submitted by: <You> Reg. No: <should be yours>

 ‘B’ Level Synopsis

Suggestion/ Notes

-- End --

14/14

Submitted by: <You> Reg. No: <should be yours>