Systems Analysis and Integration assignments
WEEK 2 REPLIES
Dillon DQ1
The objective of systems analysis is to thoroughly understand the organization’s informational needs or requirements and to document those requirements in a set of specifications. Systems design is the bridge process that takes us from requirements to solution. The objective of system design is to define, organize, and structure the components of the final solution system (Satzinger et. al 2012).
Sources
Satzinger, J. W., Jackson, R. B., & Burd, S. D. (2012). Systems analysis and design in a Changing World. Course Technology, Cengage Learning.
Pengfei DQ2
User-interface design is concerned with designing the interface that allows users to interact with the system. It includes designing screens, menus, buttons, and other visual elements that users see and interact with. System-interface design, on the other hand, is concerned with the interfaces between the system and other systems or components. It includes designing the protocols, formats, and messages used for communication.
Several diagrams developed during the analysis phase can be used for user-interface and system-interface design. Use case diagrams can be used for both. Use case diagrams show the interactions between the user and the system, which can be used to design the user interface. Use cases can also show the interactions between the system and other systems, which can be used to design the system interface.
Sequence diagrams can also be used for both user-interface and system-interface design. Sequence diagrams show the interactions between objects or components, which can be used to design the flow of control in the user interface and the messages exchanged in the system interface.
Finally, class diagrams can be used for system-interface design. Class diagrams show the classes and relationships between them, which can be used to design the data structures and objects used in the system interface.
Overall, while user-interface design is focused on designing the visual elements that users interact with, system-interface design is focused on designing the interfaces between the system and other systems or components. The use case, sequence, and class diagrams developed during the analysis phase can be used to aid in both types of design.
Majin DQ3
Both the design types are sort of similar but at the same time, there are distinct variations between them. The architectural design on one hand is a type of rough and brief blueprint for a new system or an existing system. This type of design simply gives what the project is expected to present and what kind of taskings and functions this system is capable of demonstrating. This design doesn't go in very deep into the details but gives an idea of the initial structure and outline of the system. It also gives an idea of what type of materials will be required and the precise estimation of closeout and cost factors on the selected project. Before diving into detailed design, the developers and analysts always make sure that the architectural design is prepared and approved for execution. The other type of design i.e. detail design presents deeper and elaborative features, functions, and capabilities of the system to be made. It gives more thorough information on every component of the system that is mentioned in the architectural design. The architectural design conveys a big picture of the system while the detailed design goes more inner into the system giving information such as specific amount and budget for the necessary materials, comprehensive drawings, et cetera. In short, the detailed design gives the in-depth specifications of the system being developed or modified.
Kevin DQ4
My biggest critique would mostly be towards the National University SOAR page as in my opinion is very outdated and could be improved upon. My inputs:
Functionality: The user should be able to accomplish all tasks such as view or add classes in less than 5 clicks.
Usability: The user interface design needs be updated and should be compatible across all devices such as phones, tablets, and personal computers. The user should be able to clearly identify the task they want to accomplish on the screen.
Reliability: The system should be able to be utilized with 99% uptime.
Performance: The system should be responsive to user inputs in 5ms and should be able to support more than 100 users simultaneously at any given time.
Supportability: The website and database must be designed with upgrades in mind.