Computer Sciences and Information Technology - Assignment Example

COMPUTER SCIENCES AND INFORMATION TECHNOLOGY INFORMATION TECHNOLOGY AND SYSTEMS ANALYSIS Introduction 2.1 SYSTEM REQUEST What is System Request and why do you need it? A system request is a key on keyboards for PCs which has no standard use and it is usually abbreviated as Sys Req or SysRq. The key on the keyboard can be traced back to the operator interrupt key. The interrupt key is used on IBM 3270-type console keyboards of the IBM System/370 mainframe computer that is used to cause the operating system. This allows operating systems such MVS or VM/370 console in order to give input to the operating system. Explain the steps of creating a system request document? There are steps which are followed in creating a comprehensive system request document. The first step is to create a comprehensive explanation of what is needed for an IT product concerning system request. In this case, the system request document needs to develop the context around a product fully for effectiveness. It should entail a requirement that will help developers implement their work properly. Another step is making effective interviews from various sources in order to acquire information for the requirements document. The information about an IT product may be acquired from engineers, developers, customers, IT analysts or business leaders who have essential information about needs for product development. Another step which needs to be followed is listing system requirements by outlining how the product will interact with a given system for a certain network. Identifying any constraints for the project is another step which helps in explaining restrictions within the requirements document hence acquiring guidance to those who are working on the IT product or software. Considering any interface requirements is also an important step which needs to be followed when creating a system request. The interface requirements are very important since they determine how the end-user will view the product by identifying color schemes, command button requirements and any other part of an interface which is successful. Another important step is identifying parameters such as scheduling and cost within system request since they are practical considerations which should be part of it. Working up a development plan by acquiring effective information for further instructions about development of an IT product is another essential step which should be followed in creating system request. This includes the introduction of a number of norms and examination of creativity. Establishing and inserting visuals such as graphic makeup of a certain product enable the project to be fresh and provide more details about how something will look is another step. Categorizing and organizing requirements of an IT product, is a step which needs to be properly examined in creating system request. Another step is to utilize and exercise good planning strategies which will help in constructing something that reads well as well as accessed easily by individuals. 2.2 FEASIBILITY STUDY When to conduct a Feasibility Study? Feasibility study is an analysis and evaluation of the potential of a certain proposed IT project. It is based on wide research and investigation in order to support decision making processes. A feasibility study needs to be conducted when an individual has a clearly defined outline of one or more alternative business models that are readily available for exploration. The study also needs to be done when sufficient initial investigation of alternatives to determine whether they have the potential of being viable and reliable is conducted by an individual. This means that a much early exploration and investigation of a particular business idea about an effective study should be conducted when one need to conduct a feasibility study. The feasibility study also need to be conducted when feasibility money investigating ideas are put in place in order to make for example, few phone calls in an IT based business. What is the deliverable of Feasibility Study? The deliverable of the feasibility study in relation to Information Technology depends on models and tools such as User Stories, Flowcharts and Root Analysis in order to describe relevant information of the business problem in the context. Te deliverable of the IT feasibility study also entails quantitative and qualitative techniques like Benefit Analysis vs. Cost in order to rate and effectively analyze IT solutions availability. It will also include the best alternatives to any source and implementing a particular business context concerning IT products. Focusing on cost and risk efficiency of implementation, it helps in saving a lot of money and time when looking at the deliverable of feasibility study context. 3.1 BUSINESS PROCESS ANALYSIS What is Technology Analysis? Technology analysis is the application or use of statistics, economic trends and market data in determining the financial strength status of a particular technology sector. Describe and list the required activities for BPA, BPI, and BPR. The business process automation (BPA) is a technique which entails business requirements which are basically outlined in the system request focus on examining technology concerning computers in the context of activities in an IT based business. Problem analysis activities entail managers and users, who identify problems, describe and solve them in the system of a certain business entity. Root Cause Analysis entails ideas which are produced to be problems’ solutions in a certain business. Individuals must look at the nature of the problem in order to come up with a proper solution. The analysis focuses first on identifying and generating a list of problems with the current system of a particular product. It then prioritizes the problems following an order of their importance. The Business Process Improvement (BPI) contains activities of certain requirements which enhance changes that are moderate in operations in an organization. Technology offers new opportunities hence giving these changes an advantage of improving effectively and efficiently. In Business Process Improvement (BPI) entails an activity of Duration Analysis. It is used to examine and determine the total amount of time taken to perform a certain activity in a process of business input and output. The Business Process Reengineering (BPR) entails activities which are related to product outcome, elimination of unnecessary processes and technology. Organizations require an activity of introducing a new technology which can improve its quantity and quality output. They ought to do away with or eliminate inappropriate existing technologies which are ineffectively used in business entities. What is Activity Elimination? Activity Elimination is the removal of an inappropriate existing practice of activities in an IT organization to replace effective and convenient ones. For example, an organization can practice elimination of approvals or signoffs by individuals on activities they have little knowledge about. What are the objectives of Business Process Analysis Techniques? The objectives of Business Process Analysis Techniques are many in number. One of the objectives is to eliminate certain problems in order to improve with significant values of a business. Another objective is to minimize costs and maximize profits in business entities so as they can develop and improve. An objective of establishing and introducing of new technologies in businesses is achieved through business process analysis techniques. What is Outcome Analysis in BPR? The Outcome Analysis in Business Process Reengineering (BPR) focuses on understanding the fundamental outcomes which provide customers with values which help them produce best qualities. What is Time Analysis in BPR? Time Analysis in Business Process Reengineering (BPR) is an analysis where time is considered to be the key factor towards establishing an effective output in IT based businesses. 3.2 REQUIREMENTS GATHERING Explain why Requirements Gathering using different techniques is important? Requirement Gathering using different techniques in a certain IT based business is very important. Techniques such as Questionnaires, Observation and Interview are used in that case. A technique of using interviews to find out about certain IT product by analysts and users from other people has been examined. There is one-on-one interview whereby an individual sits down with clients who are familiar with IT context. This is used in order to acquire the intended information about IT programs which can help in maintaining and improving high system process. Use of questionnaires is important because they are used to collect regular routine data and specialized studies’ data which help IT product entities. Observation is another technique which helps in finding out relevant ideas and information about IT product systems processes. Observation is important since an individual uses his or her eyes to observe effective structures of developing system request in relation to IT products. 3.3 REQUIREMENTS DEFINATION Explain how you will develop a Requirements Definition Report. A requirement Definition System Report is developed by following some effective steps which help in establishing quality and quantity IT product output. In the first step a user requests about certain information relating to IT in action. The report is then developed by the provision of system categories of IT information through selection requesting about the content. The user then selects information categories which concerns IT products and uses the system to determine viewing options which are based on information category that is selected in context. The steps which help in developing a Requirements Definition Report are setting up a certain project, assessing a problem in context, documenting the assessment of an IT product, creating requirements for an IT product, reviewing requirements, related artifacts and managing them consistently. Understand the need for assigning weight age to and identifying criticality of each Requirement Statements. Assigning weight age and identifying each Requirement Statements critically is a very important thing. This is done through the first step of identifying relevant non-monetary attributes concerning IT products. Weighting the attributes, reflecting their importance, scoring the options to reflect how each attribute performs, testing and calculating the weighted scores and results and interpreting it in relation to IT context. 4.3 GAP ANALYSIS Why is Gap Analysis recommended before a package implementation? Gap analysis is recommended before a package implementation because it gives an effective comparison of performance which is actual with performance that is potential in an IT context. The analysis makes an IT process to exploit current resources and invest effective capital top enhance technology before a package implementation. 5.8 User Interface Design (UID) Explain the five steps process in User Interface Design The user interface explains how the system will relate and interact with the entities that are external. The process of interface designing undergoes five processes below. 1. Use of the scenario development These are the outlines in the interface of the steps to be applied at the work. The information is presented and documented in a for of a simple narration that is incorporated with the DFDs. The causes of the problems in the interface will be documented down for the sake of solving the problems. 2. Interface structure of the design All the screens should be shown in form of reports that are related showing the power of the users moving from one place to another. The DFDs should be created but be created by using the boxes and lines. There should be no standards rules to be applied and the boxes should have screens that are denoted. The movement of the lines should be shown in the DFDs. 3. Interface Standards design The elements needed in the design should be common in all the screens and reports. The design should also include the interface metaphor and the objects. This will also include the interface actions, icons and the templates. 4. Interface design prototyping With the prototyping, the screen simulation will be included in the screens. Some of the methods to be used in the design is paper, storyboarding, HTML and the language. 5. Evaluation of the interface The interface should also be evaluated. The evaluations should include the Heuristic which is the comparison of the design to the checklist. There is also walkthrough evaluation which simulates the movement within the components. There is also interactive evaluation where by the system is tried upon testing. This also includes testing methods which include the formal usability which is expensive and it is always detailed. List and explain type of Messages that can be used in a system Common elements of User Interface Design Clear This is one of the best elements in the interface design which enables the users to communicate freely. If users will never understand the interface they will be confused and never use the interface. Concise Clarity is also a good idea but when a designer can over clarify, it may affect the interface and customers may not use the interface. The definitions should be added in a recommended manner in order to avoid repetition. Never add too much of the information in order for the customers to avoid spending time to read contents of the application. Familiar The application should be familiar to the customers by making the interfaces to be intuitive. It is an application that can be naturally understood by the customers. Responsive The interface should be fast enough to avoid sluggishness making the customers to stop using the interface. The interface should be responsive to the customers and informative to alert the customers. What is the purpose of User Interface Design? The purpose of the user interface design is to deliver information to the customer that is of good visual sense and having a well plan. This includes efficiency and good skills that have experience. Why do companies build standards/themes for User Interface Design? Companies use standard themes to introduce nice graphics that are attractive and efficient to the customers. This also includes the interface’s effectiveness and capability to be user friendly. What is a prototype design? A prototype design is the process used by the designers when they are not sure of the success. A design is created to be a test, and if everything is successful it is implemented to work as the real project. Why do we have to consider User experiences in User Interface Design? People consider the user experiences because of the perfect performance needed by the customers. If a user is experienced, he has enough experience to avoid errors and approximation. Interface designing needs accuracy and determination. 5.2 End-user Training How would work environment affect user training? The environment a user is working on can affect the training of the user in terms of productivity, health and safety, comfort, job satisfaction and on the type of users one associates with. Training the user can be affected by building design where the user is never comfortable when training. The space and temperatures of the buildings can also affect the user. The relationship among the users is also an impact aspect on the training by spending time with them. The human characteristics and experience can also differ a lot in the training. When should user training be conducted? Why? The training should be conducted during the end user period because information technology does not need the learning of the end user using the application. Why different user categories need different training material content? Explain? They need different training material because they do not work on same functionality in the field. Information technology has different learning class of operations and the functions of each position needs to be treated differently. 5.5 System Documentation Identify and explain main types of system documentations. Administration This is used by the administrators to guide them about the system having the guidelines on how they are supposed to handle the system. Installation – this is the ability to show the administrator on how to install and configure a system. Procedures – this are the daily procedures used by the user as a guide when performing a task. Reference – this is a portion that explains a system fully and guides the technical users using the application. Trouble shooting – after a problem occurs in a system, a guide to troubleshoot is provided on how to solve the problem. Explain why Documentation activities are done during Software Development Life Cycle Phases? In order to come up with the right procedures in the development process for the application and inform the designers the possible right procedures to follow. It includes approval from the patent owner to prove that they are the owners of the application. When do we produce System Documentation? System documentation is produced before the planning process of the software implementation and development. This enables the designers to have the right information they need in the implementation of the system. Describe the main contents of a typical System Documentation? Principles of producing the system documentation will be needed to guide the system documentation process. Another aspect is the guidelines that will control and guide the process. Procedures and the techniques needed to be used in the system. What are possible impacts of a non-documented or a poorly documented system? The first impact is the failure of the system leading to inactivity of the system. Uses will never understand the system and they will be bored with it. There will be a loss or resources and capital spent in the system leading to loss to the system owners. 5.7 User Documentation What are the differences between Tutorials, References, and manuals? Tutorials are used in the overall study on how to maintain a system. It is a general knowledge given to the user on how to handle something. References are the specific resources used in acquiring the system information. This can be books, journals, and websites. Manuals are guidelines on how to use a system or something that has steps in its operations. 7.4 Applications development and customization What is Application Work Flow? This is the ability of the users to work in a systematic way in order to meet the customer’s requirements. What are the customizing and reporting tools for a given application? Visual studio ASP.NET Eclipse 7.5 Interfaces What are the purposes of using interfaces? They are used to pass the information to the users. To create a good relationship between the administrators and the users To have a good communication skill for the system To maintain the business easy and faster To access the customer fast and reliably When to use Interfaces and why? The interface is used to access the customer of a business. The interface acts as a communication tool between the system and the users online. SA 14.5 Project Documents What is Project Document? This are the legal project contracts used as the permits in a business. Why do we need to compile Project Document? Projects are compiled for the organization purpose in the business in order to come up with the best productivity. This also keeps the information of the business with the legal agreements. References Adamsen, P. B. (2000). A framework for complex system development. Boca Raton: CRC Press. Bjørner, D. (2006). Software engineering. Berlin: Springer-Verlag. Hice, G. F., Turner, W. S., & Cashwell, L. F. (1974). System development methodology. Amsterdam: North-Holland Pub. Co. ;. Mishra, J., & Mohanty, A. (2012). Software engineering. New Delhi, India: Dorling Kindersley. Stober, T., & Hansmann, U. (2010). Agile software development best practices for large software development projects. Heidelberg: Springer. Read More