You are on page 1of 3

Ahmet Erdem EKiN Uur Bagezer


Table of Contents 1. Introduction 1.1 Objectives and Goals 1.2 Scope of The Project 1.3 Definitions, Abbreviations and Acronyms 2. System General Description 2.1 Module/Components Overview 2.2 Programming Debates 2.3 Graphical Interface Issues 3. Design Considerations 3.1 Detailed Module/Components Overview 3.2 Assumptions, Dependencies and Main Constraints 3.3 Goals and Priorities 4. System Architecture 3.1 Comparison With Alternative Architectures 3.2 System Interface 5. System Module/Components Detailed Descriptions 6. Appendices

1. INTRODUCTION 1.1 Goals and Objectives In this Software Design Specifications (SDS) document, our main purpose is to give third parties sufficient information regarding the details of the design of our project Online Shopping System. In this first version of the document, we are planning to state these objectives roughly whereas in the second version we will broaden the scope and level of detail as well. At the end of this stage, we, as the software developers, will have a roadmap for the rest of the project.

1.2 Scope of the Project Online Shopping System is basically a website for online shopping purposes. Users will be interacting with the system and the database through a web browser. Therefore, we will have to follow some of those web standards through the development stage. The system will have a register and a login module which enables customers who are visiting and desire to purchase items to sign u and then to login to the system by an authentication method. There are several options that a logged in user can do aside from directly purchasing the desired item. User accounts will have credits which can be used to purchase items. The system automatically will give certain bonus credits to users who have purchased specific items. Moreover, users will be able to send credits to each other or can also directly send gifts. Since social interaction among the users is supported, we need to create a social network among the users as well. This part either will be limited with friendship declaration or can be further developed to specific friend actions like commenting to each others previous purchases etc. 1.3 Definitions, Abbreviations and Acronyms Not many to mention at the moment. They will be covered in the last version. 2. SYSTEM GENERAL DESCRIPTION 2.1 Module/Components Overview At the beginning, the user will be prompted a welcome screen with a register and a login module. Register module will take 6 inputs which can be increased in the next phases of the project. At this stage, if the user is not a member, she will be requested to fill the registration form with this 6 information. The register module will look up the requested username in the entire user database and will proceed to the next action if there does not exist a username as such. A password check will also be done during this procedure. This will check 2 password fields and compare them. If they are equal the process will continue with the personal information otherwise the user will be notified about the error. The welcome page will feed the login module with 2 data which are username and password. Again, database look up will be finished when these two data matches for a specific user. However, one more crucial point is that the user has to activate her account via email after registration is done. Otherwise her account will be deleted in 5 days. Browse module, like many others, will allow users to freely search and look for many items. 2.2 Programming Debates From our several debates and discussion we have concluded to develop our project in .NET environment.

2.3 Graphical Interface Issues Since we are developing a website (some services along with it) we need to work on the outlook as well. JavaScript and jQuery present nice functionalities to fulfil the needs of the website. Another advantage of JavaScript is that it is completely client side allowing server to behave more freely. Certain jQuery effects and CSS knowledge is required.