Web site construction
Data Collecting [ 18 ] An organization always has a main purpose; it can be selling cars, teaching, or providing web solutions. In addition to this, every organization has sub-activities like human resource management, payroll, and marketing. The approach to data collecting will vary, depending upon the exact area we are dealing with. Let’s say we learn that our car dealer also operates a repair shop, which has its own inventory, along with a car rental service. Do we include these inventories in our analyzing tasks? We have to correctly understand the place of this new information system in its context. When preparing a data model, the biggest challenge is probably to draw a line, to clearly state where to stop. This is challenging for various reasons: Our user might have only a vague idea of what they want, of the benefits they expect from the new system Conflicting interests might exist between our future users; some of them might want to prioritize issues in a different way from others, maybe because they are involved with the tedious tasks that the new system promises to eliminate We might be tempted to improve enterprise-wide information flow beyond the scope of this particular project It’s not an easy task to balance user-perceived goals with the needs of the organization as a whole. Modular Development It is generally admitted that breaking a problem or task into smaller parts helps us to focus on more manageable units and, in the long run, permits us to achieve a better solution, and a complete solution. Having smaller segments means that defining each part’s purpose is simpler and that the testing process is easier as a smaller segment contains less details. This is why, when establishing the system boundaries, we should think in terms of developing by modules. In our case study, a simple way of dividing into modules would be the following: Module 1: car sales Module 2: car inventory Delivering an information system in incremental steps can help reassure the customer about the final product. Defining the modules and a schedule about them can motivate users and also the developers. With a publicized schedule, everyone knows what to expect. With the idea of modules comes the idea of budget and the notion of priorities for development. Do we have to deliver the car sales module before or after the inventory module? Can those modules be done separately? Are there some constraints that must
Note: If you are looking for cheap and reliable webhost to host and run your mysql application check Vision mysql hosting services