April 9, 2002 at 8:31 am
What is Functional Design ?
(Application Level and Database Level.)
April 9, 2002 at 10:27 am
Functional Design overall consists of the following two steps:
ANALYZE SYSTEM REQUIREMENTS
This task determines requirements of the system and develops a storyboard to demonstrate the intended approach. It is also used to gain buy-in from project mangement, key stakeholders, and end users.
1. Assess end users and other audiences to determine system functionality.
2. Examine training and documentation content to determine requirements for template functionality, potential conversion routines, and navigation.
3. Assist the client organization in analyzing the technical infrastructure and determining system requirements. Consider current and future LAN / WAN infrastructure, existing and expected configuration of the various SAP instances and clients, standard desktop configuration (including web browser capabilities), and location and distribution of end users at all sites.
4. Create a storyboard to facilitate the discussion of system requirements and functionality. The storyboard is a series of slides or diagrams that show what types of materials are to be delivered, how the materials are organized, and how end users will be able to navigate to the materials they need.
5. Prepare a requirements document for the online system as the final step prior to the design of the system. The requirements document contains information on how the solution integrates with existing technical architectures at all end user sites and the specifics of navigation and access methods to the various types of material. The document outlines the system architecture, end user interface, and detailed functional design. System objectives and concept of operation are discussed as are the characteristics of intended end users. The details of each online format and function are documented as they were presented with the storyboard. Each primary screen is presented and discussed. Development methodologies, processes, and tools are documented in addition to standards and conventions.
DESIGN SYSTEM & ONLINE PROTOTYPE:
This task creates the system architecture and functional design. Design activities are developed from the requirements document for the prototype. Content creation and custom automation/conversion tools are selected and developed.
1. Validate the system analysis results and determine online navigation routines.Verify the training curriculum developed during the analysis acitivty and use it to provide guidance on how to organize the information.
2. Investigate the technical feasibility of proposed solutions with regard to infrastructure issues.
3. Create a functional model (prototype) of the proposed online support tool. The prototype will verify the end user interface, functionality, and technical feasibility of the design. This is a significant step in ensuring that the end users, training team, and project management are in complete agreement on the final system’s look and function. Using the information obtained earlier in the process, determine the appropriate set up for the hierarchy. Configure the hierarchy to support prototype development. This configuration will be used by the developers as they check materials into the online system and by the end users as they access content for support on the job.
4. Place content online in the system. An important aspect of the prototype phase is to see how the material will look online. Samples of all components of the classroom and online performance support that will be available should be included in the prototype.
5. Plan and design authoring processes, standards, and conversion routines.
"Doing easily what others find difficult is talent; doing what is impossible for talent is genius." -
Henri-Frederic Amiel
"Real knowledge is to know the extent of one's ignorance." - Confucius
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply