Management Information Systems - Research Paper Example

Management Information Systems Table of Contents Abstract 1 Introduction 2 Scope 2 Domain 3 Goals 3 Limitations 3 System main functionalities and Requirements 4 Requirements 5 Hardware requirements: 5 Software requirements: 5 System Development 7 Human Resources: 7 Technical Users 7 Time Resources 9 Cost 9 Outsourcing (Services) 10 Architectural models 10 Conclusion 12 References 12 Abstract The emergence of internet has changed the customary business practice. Now ecommerce has changed the overall structure of the business and trading. This transformation is due to better access to market. The ecommerce provides more ease regarding the acquiring the products and services through the internet. The aim of this paper is to analyze the implementation of the web based ecommerce system. This system will offer the better user support and facility of the online dealing. Introduction Famazon.com is an online store that sells books and music through the internet website. Famazon.com is the second largest online seller in the United States and has outgrown their current systems. They transact all of their business online and inventory is maintained through third party suppliers. Now Famazon.com has decided to develop their own online transact for their online business and inventory. This system will be an independent structure regarding online management and administration of the web based transaction. In this report I will present the detailed analysis of the client-server system implementation and development. This report will provide a deep insight into the overall handling of the each phase of the project. These phases include the hardware, software, and systems implementation details. Then I will also talk about the architecture and distributed computing paradigm for this client-server system implementations. Here this report also provides the details regarding the database management systems. The discussion about the availability, reliability, performance, and scalability will also be discussed. Scope This project is intended to enhance the overall working and performance of the Famazon.com. This project is aimed to provide a better competitive edge. This will also reduce the transact cost of the online business and inventory services expenses due to third party suppliers. This project will also enhance the overall capacity of the order processing of the Famazon.com. The extra expenses will reduce down those are linked to the third party suppliers services. Domain This project will be based on the database that will be used for storing and processing of the orders. This database can also be used as the central databases for the overall organizational record keeping and management. The domain of this system will be a database that will provide a comprehensive management of the overall organizational resources. Goals In this section I will point out few main objectives regarding the effective project implementation and execution. These can also be taken as the organizational project implementation goals. In this project we have following main goals: Establishment of client server network Updating of the website Establishment of the order processing and deliver mechanism Quality assurance Gaining better competitive edge Performance enhancement Limitations In this section I will also point out few limitations regarding the implementation of this project. These limitations can be time, cost, technology or services related. First of all we have main limitation regarding the on time completion of this project. This project is basically an overall enhancement of the organizational order processing network. There is lot of time needed for the effective and on time completion of the project. We have assigned an approved time line but any small problem can cause a big problem regarding the on time completion of this project. Next we have limitation regarding the cost of this project. Cost overrun is a common problem in approximately all the projects. This project is huge and the cost overrun is also expected here. We need to establish a better working cost policy to manage and handle the cost of this project. This will ensure the completion of this project on time and within resources. The technical limitation is also expected here. The availability of some technical expertise’s are expected before the project start but there are few exceptions in this regard. Like that at any point in the project developer would not be able to handle any problem at that stage we need some technical consultation. The availability of such consultation is possible but it depends on the problem. If problem is complex then we have to suffer regarding the overall project handling. System main functionalities and Requirements In this section I will talk about the development requirements and expected functionalities of the client server solution to implement an e-commerce site for Famazon.com. for the client server solution I will discuss the requirements regarding the user driven or system driven scenarios. Here it will be examined that these requirements should be driven in an effective way to develop a better system design that will lead to more successful Famazon.com system implementation. Requirements This section will provide a deep insight into the system requirements. This section will emphasize and address each aspect of system non-functional requirements area. Hardware requirements: Pentium 4 [workstation for each Famazon.com employee] Network Equipment Servers Switches LAN structure Software requirements: Windows XP Oracle database Visual Basic and Access CASE tools Performance Parameters Here I will elaborate how the system needs to work and respond to any user request. The following given performance parameters or functional requirements for this client server architecture will present the main system features regarding its functionality. Simple interface: The system should have a simple interface that can be easily accessed. The interface should not contain any complex features and data that can make the user feel distracting. We will also need to consider about the color scheme of the website pages and links. We have to choose colors those are simple and provide a feel of lightness. The font is also a main consideration of this interface. We have to choose the font that is easy in reading and working. The order processing and shipment should be easy to manage on Famazon.com. Adoptability: The system should be adoptable both inside and out side the Famazon Ltd., because previously this organization is working on a different architecture. This transform to new system should be easy to manage and handle. It means that the Famazon Ltd. employees have to feel more ease; while working with this new system and customer should not face any trouble regarding the usage of the Famazon Ltd. website. If the system produce a feeling of overhead then it will be difficult for the user and Famazon Ltd. employees to use the system in a more effective way. Usability: The system should be usable in the scenario of its working and ease of online transaction. This new system needs to provide its user a more relaxing and satisfaction feeling for the online purchasing and shipment. Efficiency: The system should be efficient in its working and online purchasing and shipment tasks. Security: Nowadays we are facing biggest hazard from the online money frauds. Lots of people are uncertain from the online transaction. Here in our system we need to make sure that there is no security hole in the system working and online cash transaction. By this way the public will feel free regarding the online transaction and our business will gain more customers loyalty. For this purpose we will provide that facility that all data should be encrypted. System Development In this section I will talk about few systems development scenarios. Here I will first talk about the main resources that we will be required for the overall project management and execution. Human Resources: This section will present a list of the Human Resources that will be involved in the development of Famazon.com. Technical Users Here we will involve the different teams of the application developers: Analysts This team will be involved to gain main requirements and system needs System Designers System designer will develop the system logical and physical design Coders This class of programmers will code the system in the Oracle and visual basic Testers Team of tester will check the system for the potential errors and faults Quality Assurance The aim of quality assurance team is to check the system for the better system working and fault free working. Technical Staff Will be involved in the up-gradation of the physical client server network of the company Non-Technical Users This category of the users will be involved for the gaining of the basic requirements and system features of the Famazon.com. For instance we will involve the following people for this system development: Customer Operatives IT operatives Famazon.com manager Employees for the new system handling Network management staff Any class of common persons who is interested in the online Famazon.com (will give there comments regarding system design and working) Time Resources In this section I have presented the overall schedule of the project execution and management. Here I have accessed that time period of three months will be enough for the overall system development and deployment. No. Activity Time Allocated (days) 1 Requirements assessment 10 2 System design 10 3 Development 30 4 Hardware implementations 20 5 Testing 10 6 Quality assurance and performance analysis 10 Cost This section is about the cost estimates of the project. Here we have tried to assign enough cost to each project activity so that the project implementation becomes a success. This project will cost $90000. No. Activity Cost (In $) 1 Analysis and Design 20000 2 Development and testing 30000 3 Hardware and additional software 40000 4 Technical support 10000 5 Training 5000 6 Others 5000 Outsourcing (Services) In this section I will discuss about the need of the third party vendors and suppliers for the overall system development and implementation. First of all we need the technical support for the overall system development. For the establishment of the Famazon.com client server set-up we will require the outsourcing regarding the effective system development. For this purpose we will consult with some software developer firm. In the hardware implementation for new Famazon.com’s client server set-up we will require the technical support for overall system establishment. We will hire some technical experts for the successful and error free network handling. Architectural models In this section I will present a UML based architectural model that will provide an overview of the overall working and interaction of the system. I have researched and found that the USE CASE diagram can provide a detailed and complete overview of the Famazon.com’s client server set-up. We can have a clear overview of the main system users and responses against that system call. Use case diagram Error: Reference source not found Sn Account Renewal Information Error: Reference source not found Conclusion In this report I have presented a complete overview of the Famazon.com’s client server architecture development and planning. I have discussed about the main project implementation details and plans. This report presents a complete overview of the main project tasks and their exaction details. I hope that this report will provide a deep insight into the overall project execution. References Allen, R.J., (1997). A Formal Approach to Software Architecture, PhD thesis, Software Engineering Institute, Carnegie Mellon University Bass, L., Clements, P. and Kazman, R., (2003). Software Architecture in Practice, 2nd Edition. Addison Wesley, Reading, MA, USA Jawadekar, W. S. (2004). Software Engineering: Principles and Practice. New York: McGraw Hill. Kenneth Laudon, J. L. (1999). Management Information Systems, 6th Edition. New Jersey: Prentice-Hall. Norton, P. (2001). Introduction to Computers. Singapore: McGRAW-HILL. Pressman, R. S. (2001). Software Engineering: A Practicioner's Approach, 5th Edition. London: McGraw Hill. Sommerville, I. (2004). Software Engineering, 7th Edition,. New York: Pearson Education (Addison Wesley). Williams, B. (2005). Soft Systems Methodology. Retrieved April 22, 2009, from Actrix Users Home Pages: http://users.actrix.co.nz/bobwill/ssm.pdf Read More