A traditional development environment:
Influenced by compatibility issues; Existing hardware and software and legacy system requirements
Designed to run on local and wide-area company networks
Often utilize internet links and resources, but web-based features are treated as enhancements rather than core elements of the design.
Development follows 3 main paths:
in-house development, purchase of a software package/ modification, or outside consultants
Scalability can be affected by network limitations and constraints
Most applications require substantial power and resources
Security issues are less complex, than web-based systems, because the system operates on a private company network.
Systems are developed and delivered in an internet based frame work such as .NET or WebSphere.
Internet-based development treats the Web as the platform, rather than a communications channel.
Web-based systems are easily scalable, and can run on multiple hardware environments.
Large firms tend to deploy Web-based systems as enterprise-wide software solutions for applications such as, customer relationship management, order processing and materials management.
Web-based software treats the software application as a service and is less dependent on computing power and resources.
When companies acquire Web-based software as a service rather than a product, they can limit in-house involvement to a minimum and have the vendor install, configure, and maintain the system by paying a fee.
Web-based software usually requires additional software called middleware, to communicate with existing software and legacy systems
Good design depends on 7 basic principals:
1) Understand the business - the designer must understand the underlying business functions and how the system supports individual, departmental, and enterprise goals. The overall objective is to design an interface that helps users perform their jobs.
2) Maximize Graphical Effectiveness - A well designed interface can help users learn a new system rapidly and become more productive.
3) Think like a user - A systems analyst should understand user experience, knowledge, and skill levels. The interface should be flexible enough to accommodate novices as well as experienced users.
4) Use models and prototypes, from a user's perspective - the interface is the most critical part of the system design because it is where they interact with the system.
5) Focus on usability - The UI should include all tasks, commands, and communications between users and the information system. The opening screen should show the main options, with each screen option leading to another screen, with more options. Too many options on a screen can be confusing.
6) Invite feedback - Even after the system is operational, it is important monitor system usage and solicit user suggestions.
7) Document everything - You should document all screen designs for later use by programmers. If using a CASE tool or screen generator, number the screen designs and save them in a hierarchy similar to a menu tree.
A document that presents the complete design for the new information system, along with detailed costs, staffing and scheduling for completing the next phase of SDLC phase - system implementation. It is a baseline against which the operational system will be measured. Oriented toward the programmers that will use it to create the necessary programs.
Management Summary - a brief overview of the project for company managers and executives
System Components - The complete design for the new system, includes user interface, outputs, inputs, files, databases, and network specs.
System Environment - Constraints or conditions affecting the systems including any requirements that involve operations, hardware, systems software, or security.
Implementation Requirements - Start-up processing, initial data entry or acquisition, user training requirements and software test plans
Time and Cost Estimates - Detailed schedules, cost estimates, staffing requirements for the systems development phase
Additional Material - Other material can be included at the end of the system design specification, insert documents from earlier phases if they would be helpful