Information Systems - Research Paper Example

Computer Dealer Management System (CDMS) ID: XY123 ABCD Contents Contents 2 PROJECT Background 3 1 AIM and objective 3 2Methodology 3 2. Entity analysis 3 2.1 Entity Relationship Diagram (ERD) 6 2.2 SQL Exempel 6 3. System Requirements 7 3.1 System Functional Requirments 7 3.1.1 The system shall provide User Based Authentication 7 3.1.1 The system shall web based order placement 7 3.1.2 The system will have the capability to add users 7 3.1.3 The system shall allow Update Record 8 3.1.4 The system shall Generate reports 8 3.1.5 The system shall allow to publish Data on Web 8 4. Building Web Interface 8 4.1 Integrating Business Intelligence 8 4.1.1 Security Requirements 8 4.1.2 Interface Requirements 9 4.1.3 Usability Requirements 9 5. Evaluation 10 References 10 1. PROJECT Background The system is envisioned to support the business purposes of a computer dealer. Presently, the business is maintaining its information on excel sheets. However, the business is planned to extend online support to its clientele on implementation of Computer Dealer Information System (CDMS). Following are the basic requirements of the proposed CDMS; 1.1 AIM and objective CDMS is the hub of activities for the business. These activities are broad based and extend all over the business domain. The Chief Executive has to have a good idea of the all the business activities. He is also responsible for selecting equipment and clientele. The CDMS is not only required to manage these activities but also required to provide decision support to Chief Executive. Moreover, it will serve as the first impression for the client at web. 1.2 Methodology CDMS will be implemented using C# language with dotNet Framework, and will also use Visual Web Pack 5.5 MS SQL Server 2000 as backend database. 2. Entity analysis CDMS will have following entities and relationships. Person It will have the personal details of all the users of the system. This entity will have one to one relationship with membership entity. per_id will be the primary key for this entity. Membership This entity will ensure the login of a user according to his membership status. The user will be granted access to various module of the application according to its membership status and membership type. A member can materialize many purchases and sales for the company. It will be weak entity whose existence depends on person. mem_id will be the primary key for this entity. per_id will be the foreign key for this entity. Login This entity will validate the login in to the system based on the membership type and membership status of the user. login_id will be the primary key for this entity. Sales This entity will maintain statistics of sales. This entity will have one-to-many relationship with membership entity. sel_id will be the Primary key for this entity. eq_id and mem_id will be the foreign key for this entity. Purchase This entity will maintain statistics of purchases by the company. This entity will have one-to-many relationship with membership entity. pur_id will be the Primary key for this entity. eq_id and mem_id will be the foreign key for this entity. Eq_catagory This entity will maintain a detailed list of all the equipment the company deals in. This entity will have one-to-many relationship with stock entity. eq_id will be the primary key for this entity. Stock This entity will maintain statistics of available stock. This entity will have one-to-many relationship with eq_catagory entity. It will be weak entity whose existence depends on person. stk_id will be the Primary key for this entity. eq_id and pur_id will be the foreign key for this entity. Customer This entity will maintain personal details of company clientele. This entity will have one-to-one relationship with order entity. cus_id will be the Primary key for this entity. Order This entity will maintain record of orders placed by the clientele. This entity will have one-to-many relationship with customer entity. ord_id will be the Primary key for this entity. cus_id will be the foreign key for this entity. 2.1 Entity Relationship Diagram (ERD) 2.2 SQL Exempel Following are the few very simple examples of SQL queries; SELECT eq_name, eq_make, eq_model FROM eq_catagory WHERE eq_make = ‘Acer Server’ SELECT eqp.eq_name Description, SUM(stk.qty) Quantity FROM eq_catagory eqp, stock stk WHERE eqp.eq_id = stk.eq_id GROUP BY eqp.eq_model Following is a simple code snippet of Page Load procedure in ASP.net where the database is being connected and a simple query is passed to database connection object; include DB = new include(); DB.setConnection(); SqlConnection con = DB.getConnection(); con.Open(); string query = "select person.per_name " + "from person " + "where person.per_id = " + Session["userid"] + ""; SqlCommand cmd = new SqlCommand(query, con); SqlDataReader reader = cmd.ExecuteReader(); while (reader.Read()) { this.setName(reader[0].ToString()); } 3. System Requirements 3.1 System Functional Requirments 3.1.1 The system shall provide User Based Authentication Rational: The system shall authenticate various users at the time of login and various system features are based on the user authentication. 3.1.1 The system shall web based order placement Rational: The system shall authenticate various users at the time of login and various system features are based on the user authentication. 3.1.2 The system will have the capability to add users Rational: As the Company extends its operations the System Manager will add new user in the system. 3.1.3 The system shall allow Update Record Rational: In case of any change in the existing credential of the various clients the system will provide a separate set of screens to edit/Update any required information in the system. 3.1.4 The system shall Generate reports Rational: The system shall generate various reports on the basis of data entered in to the system. 3.1.5 The system shall allow to publish Data on Web Rational: The system shall provide a facility to System Manager to publish data on web. 4. Building Web Interface 4.1 Integrating Business Intelligence By building a web interface we mean, building a web enabled application. At application level we have to build various forms and reports in web page format. In our case we will make web pages in dotnet using C# at backend and ASP.net as the front end language. Our database in SQL Server 2000 will be connect be connected to our application through a connection object in application. We will be build web pages for the employees of the company; these pages will only be accessible through authorized login in to the application. SSL will be implemented to ensure the security of the information while accessing the application from web. However, clients of the company can access various informational pages without establish and secure channel and login. 4.1.1 Security Requirements CDMS will verify the identity of all of its users before allowing them to use its capabilities. The security module of CDMS will be the single entry point to the system. This module will be vested with the responsibility of authenticating users. CDMS will ensure that users can only access data and services for which they have been properly authorized. CDMS will ensure that unauthorized malicious programs (e.g., viruses) do not infect the system. CDMS will ensure that confidential communications and data are kept private. 4.1.2 Interface Requirements Standard web page based Graphical User Interface (GUI). This would be inclusive of components like windows, text boxes etc. Meaningful dialog boxes to capture and display information, and also to communicate with the end user. The GUI and functionality presented to each user will vary somewhat depending upon the category of the user as determined by the login page of the application The level of user input will be kept to an absolute minimum in order to avoid typo errors from the user. Wherever possible, user input shall be facilitated with components that reduce possibilities of input-errors. 4.1.3 Usability Requirements CDMS is to be used by user with variable skill levels; hence it should be user-friendly, easy to use and should accommodate needs of all users. The time required from a user to acquire the know-how of the system should be minimal. 5. Evaluation CDMS is a mini Web Application on donNet platform. The application is designed for a small Computer Dealer and business requirement for big organizations are not catered for in this document. The database design is kept as simple as possible to avoid complexity. However, it provides all basic functionalities required for the implementation of a mini web application. SQL queries are provided only for example purposes and are not test over SQL Server 2000, which is the proposed database server for the application. Only few important functional requirements of the system are enlisted for the purpose of conciseness, however the design of the system can support many other functionalities which can be implemented while actual development of the system. This design document does not contain many related UML figure e.g. Context, Activity diagrams etc. However, it provides an adequate overview of the system as it is visualized. References Addison Wesley - UML for Database Design McGraw-Hill - SQL - The Complete Reference McGraw Hill - Database Management Systems, 2nd Edition Oreilly - .net framework essentials Internet Read More