<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Accounting Information System II (Sem 2 2017.2018) by SHARIFAH MILDA BINTI AMIRUL -</title>
      <link>https://padlet.com/sma6/hb8a14t67qkn</link>
      <description>Section S
Chapter: System Analysis &amp; Design</description>
      <language>en-us</language>
      <pubDate>2018-04-04 00:13:28 UTC</pubDate>
      <lastBuildDate>2023-02-18 05:51:14 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>Lecture 5:</title>
         <author>sma6</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248333487</link>
         <description><![CDATA[<div><strong>System Analysis</strong></div><ol><li>Analysis of current system achievement</li><li>Analysis of a system’s user needs</li><li>Information gathering techniques</li><li>System’s analysis report</li><li>Accountant role in systems analysis&nbsp;</li></ol><div><strong><br>System Design&nbsp;<br></strong><br></div><ol><li>&nbsp;User interface design</li><li>Output design</li><li>Input design</li><li>Security and control measures&nbsp;</li><li>Accountant role in systems designing</li></ol><div><br></div><div><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 00:16:53 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248333487</guid>
      </item>
      <item>
         <title>Siti Noorazura Binti Ramsa (BB15110691)</title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248347024</link>
         <description><![CDATA[<div><strong>System Analysis</strong></div><div>1. Analysis of current system achievement<br>Current systems analysis technique is used to evaluate the degree of support provided by current systems to the business activities of the enterprise. Assessments of user and technical satisfaction are performed and data, procedures and problems are analyzed. <br>The purpose of current systems analysis technique is to identify shortcomings and issues with current systems. It is used to assess the usefulness, usability, and overall user satisfaction with the current systems to facilitate decision making concerning the current systems’ strategic and tactical viability.<br> <a href="https://www.projectmanagement.com/process/popup.cfm?ID=23401">https://www.projectmanagement.com/process/popup.cfm?ID=23401</a> <br><br><br>2. Analysis of a system's user needs<br><br> The aim  is to provide a clear understanding of requirements as an early input to development projects. We help focus design work on those issues that are central to the success of a product or system in the eyes of the end-users. <br> </div><div>Typical requirements gathering and analysis methods include:</div><ul><li><em>Surveys</em> – both open-ended and focused surveys, conducted electronically or on paper.</li><li><em>Interviews</em> – typically conducted face-to-face, but also over the telephone if deemed more appropriate.</li><li><em>Focus groups</em> – whilst being poorly suited to evaluating a product, focus groups are useful for discussing possible user requirements and brainstorming ideas.</li><li><em>Field studies </em>– observing the end-user situation and the environment in which a new product or system will be used is often extremely useful in understanding user needs.</li><li><em>Evaluation of an existing product</em> – provides a range of useful information (even competitor products can be tested). Usability evaluation reveals and clarifies good and bad aspects of current solutions - valuable input to new design work.</li><li><em>Task analysis</em> – a deeper analysis of users work with a system, useful for analysing how user's work tasks should be supported by functionality in a system.</li><li><em>User personas and usage scenarios</em> – concrete and illustrative data about typical users, their characteristics, usage situation, tasks and goals. Particularly useful in supporting early user interface design work.</li><li><em>Formulation of usability goals and overall design criteria</em> – help focus and steer the design process, supporting the evaluation of early concepts, prototypes and final designs. </li></ul><div><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a></div><div><br>3. Information gathering techniques<br><br> DEFINITION<br>The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:</div><div><br></div><ul><li><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.</li><li><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.</li><li><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.</li><li><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks. </li></ul><div><br><a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a></div><div><br>4. System's analysis report<br> <br>The purpose of this report is to present the proposed system analysis for the client, Click &amp; Connect, with the intention of ensuring all stakeholders involved agree on the planned solution. Throughout the project the analysis, development, implementation and testing phases will be conducted using, the industry standard, agile development life cycle. This specifies that changes can be made if required and appropriate. The system analysis report is intended for all the project's major stakeholders: the client, the academic supervisors and the development team <br><a href="https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php">https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php</a><br><br>5. Accountant role in systems analysis<br><br><strong>First,</strong> accountants are users. All systems that process financial transactions impact the accounting function in some way. Like all users, accountants must provide a clear picture of their problems and needs to the systems professional. For example, accountants must specify accounting techniques to be used; internal control requirements, such as audit trails; and special algorithms, such as depreciation models.<br><strong> Second</strong>, accountants participate in systems development as members of the development team. Their involvement often extends beyond the development of strictly accounting information systems applications. Systems that do not process financial transactions may still draw on accounting data. The accountant may be consulted to provide advice or to determine if the proposed system constitutes an internal control risk.<br> <strong>Third</strong>, accountants are involved in systems development as auditors. Accounting information systems must be auditable. Some computer audit techniques require special features that must be designed into the system. The auditor/accountant has a stake in such systems and must be involved early in their design.  <br><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a></div><div><strong><br>System Design <br></strong>1. User interface design<br> User Interface (UI) Design focuses on anticipating what users might need to do and ensuring that the interface has elements that are easy to access, understand, and use to facilitate those actions. UI brings together concepts from <a href="https://www.usability.gov/what-and-why/interaction-design.html">interaction design</a>, <a href="https://www.usability.gov/what-and-why/visual-design.html">visual design</a>, and <a href="https://www.usability.gov/what-and-why/information-architecture.html">information architecture</a>. <br><br><a href="https://www.usability.gov/what-and-why/user-interface-design.html">https://www.usability.gov/what-and-why/user-interface-design.html</a><br><br>2.Output design<br> </div><div>The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.<br><br></div><div><br>Objectives of Output Design<br><br></div><div>The objectives of input design are −<br>-To develop output design that serves the intended purpose and eliminates the production of unwanted output.</div><div>-To develop the output design that meets the end users requirements.<br>-To deliver the appropriate quantity of output.</div><div>-To form the output in appropriate format and direct it to the right person.</div><div>-To make the output available on time for making good decisions. <br><br></div><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br>3.Input design<br> input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.</div><div><br></div><div>Therefore, the quality of system input determines the quality of system output. Welldesigned input forms and screens have following properties −<br><br></div><ul><li>It should serve specific purpose effectively such as storing, recording, and retrieving the information.<br><br></li><li>It ensures proper completion with accuracy.<br><br></li><li>It should be easy to fill and straightforward.<br><br></li><li>It should focus on user’s attention, consistency, and simplicity.<br><br></li><li>All these objectives are obtained using the knowledge of basic design principles regarding −<br><br><ul><li>What are the inputs needed for the system?<br><br></li><li>How end users respond to different elements of forms and screens.<br><br></li></ul></li></ul><div><br>Objectives for Input Design<br><br></div><div>The objectives of input design are −<br><br></div><ul><li>To design data entry and input procedures<br><br></li><li>To reduce input volume<br><br></li><li>To design source documents for data capture or devise other data capture methods<br><br></li><li>To design input data records, data entry screens, user interface screens, etc.<br><br></li><li>To use validation checks and develop effective input controls. <br><br></li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br>4.Security and control measures<br><strong> Input Integrity Controls</strong><br>Input integrity controls include a number of methods to eliminate common input errors by end-users. They also include checks on the value of individual fields; both for format and the completeness of all inputs.</div><div><br></div><div>Audit trails for data entry and other system operations are created using transaction logs which gives a record of all changes introduced in the database to provide security and means of recovery in case of any failure. <br> </div><div><strong>Output Integrity Controls </strong><br>Output integrity controls include routing codes to identify the receiving system, and verification messages to confirm successful receipt of messages that are handled by network protocol.</div><div><br></div><div>Printed or screen-format reports should include a date/time for report printing and the data. Multipage reports contain report title or description, and pagination. Pre-printed forms usually include a version number and effective date. <br><br></div><div><br>5.Accountant role in systems designing<br>Generally, people believe that insiders in every area help in making better developmental instrument. As accountants master in accounting areas, they are the most suitable and most equipped for designing information system especially system related to Accounting.  For example, design managerial accounting information system to aid management in decision making process<br><a href="http://www.accountantnextdoor.com/accountants%E2%80%99-role-in-the-accounting-information-system/">http://www.accountantnextdoor.com/accountants%E2%80%99-role-in-the-accounting-information-system/</a></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 01:53:06 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248347024</guid>
      </item>
      <item>
         <title>SYSTEM ANALYSIS</title>
         <author>jackhazlyne1</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248353101</link>
         <description><![CDATA[<div><strong>1. Analysis of current system achievement<br></strong><br></div><div>System analysis is&nbsp; a systems development phase involving the study of existing systems and work processes to identify strengths, weaknesses, and opportunities for improvement.</div><div><strong><br>2. Analysis of system's user needs<br></strong>The aim&nbsp; is to provide a clear understanding of requirements as an early input to development projects. We help focus design work on those issues that are central to the success of a product or system in the eyes of the end-users. <strong><br><br>3. Information gathering techniques<br></strong>&nbsp;Information gathering or data collection is a formal process of using research, meetings, interviews, questionnaires, sampling, and other techniques to collect information about system problems, requirements, and preferences. Techniques such as&nbsp; One-on-one interviews, Group interviews, Facilitated sessions, Joint application development (JAD), Questionnaires, Prototyping, Use cases, following people around, Request for proposals (RFPs) and Brainstorming&nbsp;</div><div><strong><br>4. System's analysis report Accountant role in system analysis<br></strong>Summarise and documents the findings of analysis activities and serves as a repository of data from which system designers can draw <strong><br><br>SYSTEM DESIGN<br>1. User interface design<br></strong>&nbsp;Defines the way in which the users will interact with the system and the nature of the inputs and outputs that the system accepts and produces.&nbsp; Manipulating design elements (images, text, colours) contents, and functionalities with the focus on user experience and interactivity. Requires an understanding of Human-Computer Interaction and user centred design principles</div><div><strong><br>2. Output design<br></strong>&nbsp;Outputs are the report that the system produces. The goal of output is to present information to users&nbsp;</div><div><strong><br>3. Input design<br></strong>&nbsp;Means designing the screens used to enter the information, as well as any forms on which users write or type information. The goal is to capture accurate information&nbsp;</div><div><strong><br>4. Security and control measures</strong></div><div>The designer can include many control features, such as Menu Bars, Toolbars, Dialog Boxes, Text Boxes, Toggle Buttons, List Boxes, Scroll Bars, Drop-down List Boxes, Option Buttons, Check Boxes, Command Buttons, Spin Bars, and Calendars&nbsp;</div><div><strong><br>5. Accountant role in system designing<br></strong>Accountant will recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood.</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:39:55 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248353101</guid>
      </item>
      <item>
         <title>Siti Fazwalina Binti Wahimin (BB15110684)</title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248353655</link>
         <description><![CDATA[<div><strong>SYSTEM ANALYSIS<br></strong><mark>1. </mark><em><mark>Analysis of current system achievement</mark></em><em><br>-</em> The systems analyst needs to know the details of current system functions: the who (the people who are involved), what (the business activity), where (the environment in which the work takes place), when (the timing), and how (how the current procedures are performed) of the business under study. The analyst must then ask why the business uses the current system. There may be good reasons for doing business using the current methods, and these should be considered when designing any new system. <a href="http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/">http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/</a> <em><br><br></em><em><mark>2. Analysis of a system's user needs</mark></em><em><br>-</em> The aim is to provide a clear understanding of requirements as an early input to development projects. We help focus design work on those issues that are central to the success of a product or system in the eyes of the end-users. <br> <a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a> <em><br><br></em><em><mark>3. Information gathering techniques</mark></em><em><br></em>-The main aim of fact finding techniques is to determine the information requirements of an organization used by analysts to prepare a precise SRS understood by user. Ideal SRS Document should:&nbsp;</div><ul><li>be complete, Unambiguous, and Jargon-free.&nbsp;</li><li>specify operational, tactical, and strategic information requirements.&nbsp;</li><li>solve possible disputes between users and analyst.</li><li>use graphical aids which simplify understanding and design.&nbsp;</li></ul><div>-There are various information gathering techniques:&nbsp;</div><ol><li>Interviewing&nbsp;</li><li>Questionnaires&nbsp;</li><li>Reviews of record, procedures and forms</li><li>Observation</li><li>Joint Application Development(JAD)</li><li>Secondary research or background reading</li></ol><div><br><em><mark>4. System's analysis report</mark></em><em><br>-</em> The aim is to provide a clear understanding of requirements as an early input to development projects. We help focus design work on those issues that are central to the success of a product or system in the eyes of the end-users. <br> <a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a> <em><br><br></em><em><mark>5. Accountant role in systems analysis</mark></em><em><br>-</em> First is as an a user.&nbsp; accountants must provide a clear picture of their problems and needs to the systems professional. <br>-Second as an auditor.&nbsp; Accountant will help to require special features that must be designed into the system. <br> <a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a><em><br><br></em><strong>SYSTEM DESIGN<br></strong><em><mark>1. User interface design</mark></em><strong><br>-</strong>User Interface for system design more focus on anticipating what users might need to do and ensuring that the interface has elements that are easy to access, understand, and use to facilitate those actions. User Interface also brings together the concepts from interaction design, visual design, and information architecture.</div><div><a href="https://www.usability.gov/what-and-why/user-interface-design.html">https://www.usability.gov/what-and-why/user-interface-design.html<br></a><br></div><div><em><mark>2.Output design</mark></em><strong><br>-</strong>Outputs design are important part of any system. Output refers to the results and information that are generated by the system. In many cases, output is the main reason for developing the system and the basis on which the usefulness of the system is evaluated. Most end-users will not actually operate the information system or enter data through workstations, but they will use the output from the system.<br>While designing the output of system, the following factors should be considered:</div><ul><li>Determine what information to present</li><li>Decide on the mode of output, i.e. whether to display, print, or "speak" the information and select the output medium</li><li>Arrange the presentation of information in an acceptable format</li><li>Decide how to distribute the output to intended recipients</li></ul><div>-These activities require specific decisions, such as whether to use preprinted forms when preparing reports and documents, how many lines to plan on a printed page, or whether to use graphics and color. The output design is specified on layout forms, sheets that describe the location characteristics (such as length and type), and format of the column heading, etc</div><div><br><em><mark>3. Input design</mark></em><strong><br>-I</strong>nputs design also important part of any system, During design of input, the analyst should decide on the following details:</div><ul><li>What data to input</li><li>What medium to use</li><li>How data should be arranged</li><li>How data should be coded i.e. data representation conventions</li><li>The dialogue to guide users in providing input i.e. informative messages that should be provided when the user is entering data. Like saying, "It is required. Don't leave it blank."</li><li>Data items and transactions needing validation to detect errors</li><li>Methods for performing input validation and steps to follow when errors occur</li></ul><div>-The design decisions for handling input specify how data are accepted for computer processing. The design of inputs also includes specifying the means by which end-users and system operators direct the system in performing actions.</div><div><br><em><mark>4. Security and control</mark></em><strong><em><br>-</em></strong><strong>System security</strong> refers to protecting the system from theft, unauthorized access and modifications, and accidental or unintentional damage. In computerized systems, security involves protecting all the parts of computer system which includes data, software, and hardware. Systems security includes system privacy and system integrity.</div><ul><li><strong>System privacy</strong> deals with protecting individuals systems from being accessed and used without the permission/knowledge of the concerned individuals.</li><li><strong>System integrity</strong> is concerned with the quality and reliability of raw as well as processed data in the system.</li></ul><div>-<strong>Control Measures<br></strong>a)<strong> </strong>Backup<br>b) Physical Access Control to Facilities<br>c) Using Logical or Software Control<br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm</a></div><div><br></div><div><em><mark>5. Accountant role in systems designing </mark></em><em><br>-</em>Accountants are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument. This function of designing AIS includes the design of managerial accounting information system to aid management in decision making processes. <em><mark><br></mark></em><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:44:03 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248353655</guid>
      </item>
      <item>
         <title>NASRIAH BINTI NASIR</title>
         <author>misslieya783</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248353813</link>
         <description><![CDATA[<div><strong>(BB15110444)</strong><br><strong>System Analysis<br></strong><br></div><ol><li><mark>Analysis of current system achievement <br></mark>Most systems are not developed from scratch. Usually, some form of information system and related procedures are currently in place. The analyst often begins the analysis by determining what elements, if any, of the current system should be preserved as part of the new system. This involves a rather detailed system survey. Facts pertaining to preliminary questions about the system are gathered and analyzed. As the analyst obtains a greater depth of understanding of the problem, he or she develops more specific questions for which more facts must be gathered. This process may go on through several iterations. When all the relevant facts have been gathered and analyzed, the analyst arrives at an assessment of the current system. Surveying the current system has both disadvantages and advantages. <br><em>Advantages of Surveying the Current System </em><br>-&nbsp; identify what aspects of the old system should be kept. Some elements of the system may be functionally sound and can provide the foundation for the new system. By fully understanding the current system, the analyst can identify those aspects worth preserving or modifying for use in the new system <br>-&nbsp; by surveying the current system, the analyst may determine conclusively the cause of the reported problem symptoms. Perhaps the root problem is not the information system at all; it may be a management or employee problem that can be resolved without redesigning the information system. We may not be able to identify the root cause of the problem if we discard the existing system without any investigation into the symptoms.<br><em>&nbsp;Disadvantages of Surveying the Current System </em>&nbsp;<br>-&nbsp; current system surveys stifle new ideas. By studying and modeling the old system, the analyst may develop a constrained notion about how the new system should function. The result is an improved old system rather than a radically new approach. An example is the implementation of an ERP system. The task of reviewing current organizational procedures may serve no purpose because the successful implementation of an ERP depends on reengineering these processes to employ the best business practices of the industry <br><a href="https://nscpolteksby.ac.id/ebook/files/Ebook/Accounting/Accounting%20Information%20System-James%20A.Hall%206%20(2008)/16.%20Part%204%20Chapter%2013%20-%20Managing%20the%20Systems%20Development%20Life%20Cycle.pdf">https://nscpolteksby.ac.id/ebook/files/Ebook/Accounting/Accounting%20Information%20System-James%20A.Hall%206%20(2008)/16.%20Part%204%20Chapter%2013%20-%20Managing%20the%20Systems%20Development%20Life%20Cycle.pdf</a>&nbsp;</li></ol><div>2. <mark>Analysis of a system’s user needs</mark></div><div><br></div><div>You can refer this link : <a href="https://www.nap.edu/read/22281/chapter/6">https://www.nap.edu/read/22281/chapter/6</a><br><br>3. <mark>&nbsp;Information gathering techniques&nbsp;</mark></div><div>As defined in the dictionary, <strong>information gathering</strong> is the act of collecting <strong>information</strong> from various sources through various means. In the literal sense,<strong>information gathering</strong> is a basic human skill necessary for undertaking basic human activities such as eating, sleeping, working etc.&nbsp;<br><br></div><div>Managing information involves gathering and distributing necessary information and assimilating them on the project management activities and processes. The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:<br><br></div><ul><li><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.</li><li><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.</li><li><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.</li><li><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks.&nbsp;</li></ul><div><a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a> <br><br>4.<mark>System’s analysis report</mark></div><div><a href="https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php#_ofdynh8m8rtb"><strong>System Vision</strong></a><br>The purpose of this report is to present the proposed system analysis for the client, Click &amp; Connect, with the intention of ensuring all stakeholders involved agree on the planned solution. Throughout the project the analysis, development, implementation and testing phases will be conducted using, the industry standard, agile development life cycle. This specifies that changes can be made if required and appropriate. The system analysis report is intended for all the project's major stakeholders: the client, the academic supervisors and the development team.<br><br>Firstly, this report will highlight the system vision by expanding on the project description, system capabilities and business benefits. The purpose of this initial section is to ensure that all stakeholders involved agree on the expectations and benefits of the system. <br><br>Secondly, in this deliverable the system requirements section is used to describe the functionality listed in the system vision and with the use of diagrams allow for all stakeholders to agree on the system requirements. With the use of a functional decomposition diagram the major subsystem for the Click &amp; Connect system have been described and all major functions identified. Alongside this a conceptual data model (entity relationship diagram) is presented to assist in explaining the main business processes and their relationships. It is expected that this diagram will change throughout the iterative development process. Following on, an architecture overview is utilised to highlight the current IT system and any proposed constraints. Finally, in the system requirements section a prioritised list of the system build plans has been included. The purpose of this section is to identify and describe the system requirements and constraints on the system.<br><br>Thirdly, the project organisation section of this report focuses on the system development approach, the team structure, the overall project plan and risk management plan. Ultimately this section will describe how the system develop will be approached with both its iterative and incremental nature in each build. A Gantt chart has been included to list the major tasks that will be carried out and the proposed timetable that will be followed. This chart, as a part of the overall project plan, includes the tasks and activities highlighted in the system overview. Alongside this, the risk management plan outlines current risks and possible impact they would have on the project completion. The intention of this section is to ensure all stakeholders are across the incremental development and risks involved with this project.<br><br>Finally, in this document a sign off sheet has been provided to ensure that the client has acknowledge the system overview report and to signal acceptance of the scope, content and expectations laid within. In this section if aspects are to be changed they need to be noted and agreed upon. As well an appendix has been included with client interactions and development artefacts. <br><a href="https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php">https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php</a><br><br>5. <mark>Accountant role in systems analysis </mark><br>&nbsp;</div><div><strong>THE ACCOUNTANT’S ROLE IN SYSTEMS STRATEGY<br></strong><br></div><div>Auditors routinely review the organization’s systems strategy. History has shown that careful systems planning is a cost-effective activity in reducing the risk of creating unneeded, unwanted, inefficient, and ineffective systems. Both internal and external auditors have vested interests in this outcome.<br><br></div><div><strong>THE ACCOUNTANT’S ROLE IN CONCEPTUAL DESIGN<br></strong><br></div><div>The accountant plays an important role in the conceptual design of the system. He or she must recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood. These issues need not be specified in detail at this point, but they should be recognized as items to be addressed during the construct phase of the system. Furthermore, the auditability of a system depends in part on its design characteristics. Some computer auditing techniques require systems to be designed with built-in audit features. Such features require resources and need to be considered at conceptual design.<br><br></div><div><strong>THE ACCOUNTANT’S ROLE IN SYSTEMS SELECTION<br></strong><br></div><div>The economic feasibility of proposed systems is of primary concern to accountants. Specifically, the accountant should ensure that:<br>&nbsp;</div><blockquote>• Only escapable costs are used in calculations of cost-savings benefits.<br><br>• Reasonable interest rates are used in measuring present values of cash flows.<br><br>• One-time and recurring costs are completely and accurately reported.<br><br>• Realistic useful lives are used in comparing competing projects.<br><br>• Intangible benefits are assigned reasonable financial values.<br><br></blockquote><div>Errors, omissions, and misrepresentations in the accounting for such items can distort the analysis and result in a suboptimal decision. <br><a href="https://books.google.com.my/books?id=MjRBBAAAQBAJ&amp;pg=PA573&amp;lpg=PA573&amp;dqbl&amp;ots=u-0PSzLneH&amp;sig=-jtBIcq4WwnMZ4XgtKxoqbAMR9Y&amp;hl=en&amp;sa=X&amp;ved=0ahUKEwihzrGZ7aDaAhWLYo8KHc3RBs8Q6AEIKDAA#v=onepage&amp;q&amp;f=false">https://books.google.com.my/books?id=MjRBBAAAQBAJ&amp;pg=PA573&amp;lpg=PA573&amp;dqbl&amp;ots=u-0PSzLneH&amp;sig=-jtBIcq4WwnMZ4XgtKxoqbAMR9Y&amp;hl=en&amp;sa=X&amp;ved=0ahUKEwihzrGZ7aDaAhWLYo8KHc3RBs8Q6AEIKDAA#v=onepage&amp;q&amp;f=false</a><br><br></div><div><strong>System Design&nbsp;<br></strong><br></div><ol><li>&nbsp;User interface design</li></ol><div>What is user interface design?</div><div>User interface (UI) design is the design of user interfaces for software or machines, such as the look of a mobile app, with a focus on <em>ease of use</em> and <em>pleasurability</em> for the user. UI design usually refers to the design of graphical user interfaces—but can also refer to others, such as natural and voice user interfaces.<br><br></div><div>Since software is intangible, the only way a user can control or interact with it is through a designed user interface. A well-designed user interface creates a user experience that the designer intended and/or a user experience that the user appreciates.<br><br></div><div>Many user interfaces are designed with a focus on <em>usability</em> and <em>efficiency</em>. Users should be able to achieve their goals as efficiently as possible, without focusing too much on the user interface itself. In that sense, a well-designed user interface becomes effectively <em>invisible</em> to those using it. In other words, they interact directly with the ‘reality’ the design portrays without reckoning on the point that, for example, thumbing button icons through the glass screens of their handheld devices is responsible for producing changes in what they see. However, usability and efficiency might not be the only measure of a well-designed user interface; a user interface might be designed to create a fun and pleasurable experience for users instead (e.g., in games).<br><br></div><div>At the other end of the spectrum, designers can—unethically—deliberately design user interfaces that are confusing—in order to trick users into purchasing or signing up for things they might not be interested in. These user interfaces are known as <em>dark patterns</em>. Examples of dark patterns include add-ons that are included by default (e.g., additional luggage allowance when booking air tickets), and intentionally complicated processes meant to deter users (e.g., long and confusing pages to unsubscribe from email newsletters). <br><br>More information about UI:<br><a href="https://www.cs.umd.edu/~atif/Teaching/Spring2011/Slides/8.pdf">https://www.cs.umd.edu/~atif/Teaching/Spring2011/Slides/8.pdf</a> <br><br>2. Output design<br>What is output design?<br> A <strong>Design Output</strong> is a drawing or specification or manufacturing instruction. <strong>Design Outputs</strong> describe all the components, parts, and pieces that go into your medical device. <strong>Design Outputs</strong> describe all assemblies and sub-assemblies of your product. <br><a href="https://www.greenlight.guru/blog/defining-design-inputs-and-design-outputs">https://www.greenlight.guru/blog/defining-design-inputs-and-design-outputs</a> <br><br><em>Output design objectives</em></div><div><strong>•Serve the intended purpose&nbsp;</strong></div><div><strong>•Deliver the right quantity of output&nbsp;</strong></div><div><strong>•Deliver it to the right place&nbsp;</strong></div><div><strong>•Provide output on time&nbsp;</strong></div><div><strong>•Choose the right method <br><br></strong><em>Types of output<br></em>•<strong>Internal outputs</strong> stay inside the system to support the system's users and managers&nbsp;</div><div>•<strong>External outputs</strong> leave the system to trigger actions on the part of their recipients or confirm actions to their recipients&nbsp;</div><div>–<strong>Turnaround outputs </strong>are those which are typically implemented as a report eventually re-enters the system as an input <br>•<strong>Detailed Reports:</strong>&nbsp;</div><div>–Present information with little or no filtering or restrictions.&nbsp;</div><div>–Some detailed reports are historical in nature.&nbsp;</div><div>–Detailed reports confirm and document the successful processing of transactions and serve as an audit trail for subsequent management inquiry.&nbsp;</div><div>•<strong>Exception Reports:</strong>&nbsp;</div><div>–Filter data before it is presented to the manager as information.&nbsp;</div><div>–Exception reports only report exceptions to some condition or standard. <br><a href="http://www.nku.edu/~sakaguch/ifs310/Week8.ppt">http://www.nku.edu/~sakaguch/ifs310/Week8.ppt</a></div><div><br>3.Input design<br>&nbsp;What is input design?<br>&nbsp;<strong>Input Design</strong> is the process of converting a user-oriented description of the <strong>input</strong> into a computer-based system. This <strong>design</strong> is important to avoid errors in the data <strong>input</strong> process and show the correct direction to the management for getting correct information from the computerized system. <br><a href="https://www.slideshare.net/madhukarreddy007/input-and-output-design">https://www.slideshare.net/madhukarreddy007/input-and-output-design</a> &nbsp;</div><div>•<strong>Batch input</strong>&nbsp;</div><div>–<strong>Key-to-disk (KTD)</strong> and <strong>key-to-tape (KTT)</strong>&nbsp;</div><div>•<strong>On-line input</strong>&nbsp;</div><div>–<strong>graphical user interface (GUI)</strong>&nbsp;</div><div>–<strong>Remote batch</strong>&nbsp;<br><br></div><div><strong>Batch input </strong>is the oldest and most traditional input method. Source documents or forms are collected and then periodically forwarded to data entry operators, who key the data using a data entry device that translates the data into a machine-readable format.&nbsp;</div><div><br>The most common medium for batch input data are <strong>Key-to-disk (KTD)</strong> and <strong>key-to-tape (KTT)</strong> workstations that transcribe data to magnetic disks and magnetic tape, respectively.&nbsp;</div><div><strong><br>On-line input</strong> is the capture of data at its point of origin in the business and the direct inputting of that data to the computer, preferably as soon as possible after the data originates.&nbsp;</div><div><br>The system user directly enters the data when or soon after that data originates. No data entry clerks are needed! There is no need to record data onto a medium (paper and such) that is later input to the computer; this input is direct! If data is entered incorrectly, the computer's edit program detects the error and immediately requests that the operator make a correction. <br><a href="http://www.nku.edu/~sakaguch/ifs310/Week8.ppt">http://www.nku.edu/~sakaguch/ifs310/Week8.ppt&nbsp;</a></div><div><br>4. Security and control measures</div><h1>Accounting Information Systems &amp; Security</h1><div>Accounting systems contain confidential information that should be kept safe and secure at all times. The consequences of unauthorized access can be devastating--from identity theft problems to loss of irreplaceable data. When accounting data is changed or deleted on purpose or by chance, it creates havoc in the accounting department, calling into question the reliability or accuracy of all data.<br>a) <strong>Physical Security</strong></div><div>A small business should safeguard its computer systems against losses and theft. Keep systems and servers in a safe place not exposed to the elements. Usually accounting equipment is kept inside offices where doors can be locked, limiting unauthorized access. Make sure cables connecting accounting equipment are safe and away from people tripping on them or rodents destroying them. Keep cables and switches in a locked environment. If you're using wireless connections for network or Internet access, follow security protocols; it is relatively easy to hack into wireless systems. If you use laptop computers, consider purchasing software that tracks the whereabouts of the computer. In 2008, a laptop computer was stolen every 53 seconds from restaurants, airport lounges and hotel rooms, according to the Gartner Group. To manage this risk, many businesses use a LoJack for computers that can be downloaded from the Internet.<br><br></div><div>b)<strong> Authentication</strong></div><div>All your systems should have login IDs and passwords that authenticate the user, confirming that he is allowed to use the computer. Do not share passwords and change them periodically. Many systems can be set up to automatically request a password change after 90 days, for example. The authentication process usually involves giving rights to users; not all users have access to all information. Profiles can be set up giving certain users access only to the accounts payable module, while others can have access to reports only, limiting the risk of misuse of data.<br>c)<strong>Virus Protection</strong></div><div>Computers are subject to viruses and malware that affect how they operate. Some viruses allow for system intrusion--a hacker can get inside the system and create problems. With the Internet usage, the threat of viruses and malware is real, making the use of anti-virus software, firewalls and other security measures a must. A virus attack can bring an entire accounting system down, making it unusable and ineffective. Sometimes certain viruses can disrupt a system so severely that it may need to be wiped out or replaced completely. The fix can be expensive; it is better to take preventive measures to protect systems upfront.</div><div>d)<strong> Backup</strong></div><div>A standard security procedure with accounting systems is to back up data and save the backup in a safe place outside the premises. The point is that if something happens to the system, such as fires, floods or other losses, data is safe and can be restored. A good security measure is to perform overnight backups as well as to restore backups once in a while to make sure the data is safe and usable.</div><div>e) <strong>Considerations</strong></div><div>When your system needs to be fixed, you may be opening your files and confidential information to those who repair the system. Texas requires special licensing for those who repair computers, with penalties for those who skirt this law. When a computer system used for accounting is sold or given to another party, it may still contain confidential information in its hard drive. Get your system cleaned up by a professional before donating or selling it.<br><a href="http://smallbusiness.chron.com/accounting-information-systems-security-3955.html">http://smallbusiness.chron.com/accounting-information-systems-security-3955.html</a><br><em>Other notes: </em><a href="https://bus206.pressbooks.com/chapter/chapter-6-information-systems-security/">https://bus206.pressbooks.com/chapter/chapter-6-information-systems-security/</a><br>&nbsp;</div><h1>A<strong>ccounting Control Procedures&nbsp;</strong></h1><h1>Internal controls are systems and procedures designed to ensure that all employees perform their duties ethically and honestly. Accounting controls deal specifically with the integrity of internal financial information and the accuracy of financial reports provided to outsiders. Establishing effective accounting control procedures early in your small business helps to create a culture of ethical financial management.&nbsp;</h1><div>&nbsp;</div><div>a) <strong>Cash Control</strong></div><div><br>Control of cash is one of the most important aspects of an internal accounting control system. Allow only a few trusted employees to make cash deposits, and require these employees to make deposits as soon and as frequently as possible. Keep records of all deposits--both internally generated records and bank deposit slips--and compare them to your bank statement each month. Hold cash in a secure location when it is on hand. Keep prepared deposits in a locked safe until the deposits are made, and secure cash registers with individual authentication so that you know who accessed which register at which times. Require approval from a select few employees for all cash disbursements, including payroll, accounts payable and refunds to customers.<br><br></div><div>b)<strong> Separation of Duties</strong></div><div><br>Assign separate cash handling and accounting duties among various staff members, and even various departments, if possible. For example, do not allow the person who makes bank deposits to be the only one running the cash register, and do not allow the person who places supplies orders to sign off on checks to suppliers. Make sure that cash reporting responsibilities are spread out enough to prevent theft by collusion. This can be done by giving some responsibility to front-line employees, some to front-line managers, and some to upper-level managers.&nbsp;<br>&nbsp;</div><div>c) <strong>Documentation</strong></div><div><br>Store copies of all cash register tapes, receipts, invoices, cancelled checks and any other documentation that records cash transactions. Use these documents as a paper trail to investigate cash losses and discrepancies between internal records and bank statements.<br><br></div><div>d)<strong> Information Security</strong></div><div><br>Implement physical and electronic security measures to ensure the safety of financial information. Store sensitive documents in secure areas, such as locked filing cabinets that are accessible only to select employees. Protect financial data stored on your company network by hiring a network administration team or contracting with a third-party network security company. Anyone with physical or electronic access to financial data can alter, replace, steal or destroy evidence of theft or other financial mismanagement.<br><br></div><div>e) <strong>Audits</strong></div><div><br>Obtain third-party accounting audits, from time to time, to get an outsider's look into your financial control systems. Only work with auditors who have no material connection to your company or employees. Remember that you need auditors to discover the truth about your financial picture, even if it is bad news. Using a third-party auditor to discover financial mismanagement within your company can save you from undergoing costly litigation or financial turmoil in the future <br><a href="http://smallbusiness.chron.com/accounting-control-procedures-3938.html">http://smallbusiness.chron.com/accounting-control-procedures-3938.html</a></div><div><br></div><div>5. Accountant role in systems designing<br>&nbsp;</div><div><strong>THE ACCOUNTANT’S ROLE IN CONCEPTUAL DESIGN<br></strong><br></div><div>The accountant plays an important role in the conceptual design of the system. He or she must recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood. These issues need not be specified in detail at this point, but they should be recognized as items to be addressed during the construct phase of the system. Furthermore, the auditability of a system depends in part on its design characteristics. Some computer auditing techniques require systems to be designed with built-in audit features. Such features require resources and need to be considered at conceptual design.<br>&nbsp;&nbsp;</div><div><a href="https://books.google.com.my/books?id=MjRBBAAAQBAJ&amp;pg=PA573&amp;lpg=PA573&amp;dqbl&amp;ots=u-0PSzLneH&amp;sig=-jtBIcq4WwnMZ4XgtKxoqbAMR9Y&amp;hl=en&amp;sa=X&amp;ved=0ahUKEwihzrGZ7aDaAhWLYo8KHc3RBs8Q6AEIKDAA#v=onepage&amp;q&amp;f=false">https://books.google.com.my/books?id=MjRBBAAAQBAJ&amp;pg=PA573&amp;lpg=PA573&amp;dqbl&amp;ots=u-0PSzLneH&amp;sig=-jtBIcq4WwnMZ4XgtKxoqbAMR9Y&amp;hl=en&amp;sa=X&amp;ved=0ahUKEwihzrGZ7aDaAhWLYo8KHc3RBs8Q6AEIKDAA#v=onepage&amp;q&amp;f=false&nbsp;</a></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:45:15 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248353813</guid>
      </item>
      <item>
         <title>LIM TZE WANG</title>
         <author>tzewanglim</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248353963</link>
         <description><![CDATA[<div>BB15110347</div><div><strong>System Analysis</strong></div><ol><li><strong>Analysis of current system achievement</strong></li></ol><div>The systems analyst needs to know the details of current system functions: the who (the people who are involved), what (the business activity), where (the environment in which the work takes place), when (the timing), and how (how the current procedures are performed) of the business under study. The analyst must then ask why the business uses the current system. There may be good reasons for doing business using the current methods, and these should be considered when designing any new system.<br><a href="http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/">http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/</a></div><div><strong>2.Analysis of a system’s user needs</strong><br>User need's analysis as a valuable tool to enhance user satisfaction.&nbsp; User Needs Analysis is part of the process of developing a site that will successfully meet the needs of prospective users. In addition to identifying the key needs, it can help balance potential conflicts in the desires of the site owners, stakeholders and target audience groups.&nbsp; As well as identifying and prioritising the site goals of visitors, User Needs Analysis will help determine the technological requirements necessary for them to achieve those goals. <br><a href="http://usability.com.au/research/needs-analysis/">http://usability.com.au/research/needs-analysis/</a><br><br><strong>3.Information gathering techniques</strong><br>Managing information involves gathering and distributing necessary information and assimilating them on the project management activities and processes. The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:<br><br></div><ul><li><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.</li><li><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.</li><li><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.</li><li><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks.</li></ul><div><a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a></div><div><br><strong>4.System’s analysis repor<br>Accountant role in systems analysis </strong><br>The report should be as long as necessary to record fully (1) what was done by the project team, (2) what the team's findings are, and (3) what recommendations, including further courses of actions, are being made by the project team.<br><a href="https://www.ischool.utexas.edu/~wyllys/SAEMaterials/stylesysanlrpt.html">https://www.ischool.utexas.edu/~wyllys/SAEMaterials/stylesysanlrpt.html</a></div><div><strong><br>System Design&nbsp;<br></strong><br></div><ol><li>&nbsp;User interface design</li></ol><div><strong>-</strong>User Interface for system design more focus on anticipating what users might need to do and ensuring that the interface has elements that are easy to access, understand, and use to facilitate those actions. User Interface also brings together the concepts from interaction design, visual design, and information architecture.</div><div><a href="https://www.usability.gov/what-and-why/user-interface-design.html">https://www.usability.gov/what-and-why/user-interface-design.htm</a><br><strong>2.Output design</strong></div><div><strong>-</strong>Outputs design are important part of any system. Output refers to the results and information that are generated by the system. In many cases, output is the main reason for developing the system and the basis on which the usefulness of the system is evaluated. Most end-users will not actually operate the information system or enter data through workstations, but they will use the output from the system.<br>While designing the output of system, the following factors should be considered:</div><ul><li>Determine what information to present</li><li>Decide on the mode of output, i.e. whether to display, print, or "speak" the information and select the output medium</li><li>Arrange the presentation of information in an acceptable format</li><li>Decide how to distribute the output to intended recipients</li></ul><div>-These activities require specific decisions, such as whether to use preprinted forms when preparing reports and documents, how many lines to plan on a printed page, or whether to use graphics and color. The output design is specified on layout forms, sheets that describe the location characteristics (such as length and type), and format of the column heading, etc<br><strong>3.Input design</strong></div><div>input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.<br>Therefore, the quality of system input determines the quality of system output. Well designed input forms and screens have following properties −<br><br></div><ul><li>It should serve specific purpose effectively such as storing, recording, and retrieving the information.<br><br></li><li>It ensures proper completion with accuracy.<br><br></li><li>It should be easy to fill and straightforward.<br><br></li><li>It should focus on user’s attention, consistency, and simplicity.<br><br></li><li>All these objectives are obtained using the knowledge of basic design principles regarding −<br><br><ul><li>What are the inputs needed for the system?<br><br></li><li>How end users respond to different elements of forms and screens.</li></ul></li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><strong>4.Security and control measures&nbsp;</strong></div><div><strong>Input Integrity Controls</strong><br>Input integrity controls include a number of methods to eliminate common input errors by end-users. They also include checks on the value of individual fields; both for format and the completeness of all inputs.</div><div><br></div><div>Audit trails for data entry and other system operations are created using transaction logs which gives a record of all changes introduced in the database to provide security and means of recovery in case of any failure.&nbsp;<br>&nbsp;</div><div><strong>Output Integrity Controls </strong><br>Output integrity controls include routing codes to identify the receiving system, and verification messages to confirm successful receipt of messages that are handled by network protocol.</div><div><br></div><div>Printed or screen-format reports should include a date/time for report printing and the data. Multipage reports contain report title or description, and pagination. Pre-printed forms usually include a version number and effective date. <strong>5.Accountant role in systems designing&nbsp;</strong></div><div>The role of accountant has expanded due to the development of the accounting information of various business sectors, on the one hand, and the increase of the volume and the complexity of the information, on the other hand; the accountant shall play an active and effective role in the processes of designing the systems in order to achieve an effective internal system as well as the needs of accounting information users. There is no doubt the success of developing the system requires the necessity of participation of accountants in establishing and developing that system. The effective method of applying the participation principle is represented by the ability of system to involve the accountants not only in one stage of the development of the system but all stages of system development.<br><a href="http://bepls.com/beplsoctober2015/19.pdf">http://bepls.com/beplsoctober2015/19.pdf</a></div><div><strong><br>-</strong></div><div><br><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:46:18 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248353963</guid>
      </item>
      <item>
         <title>DARYUNI BINTI DAFRI </title>
         <author>daryunidafri</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248354001</link>
         <description><![CDATA[<div>(BB15110173)<br> </div><div><strong><mark>System Analysis</mark></strong></div><ol><li>Analysis of current system achievement</li></ol><div> </div><div>Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. One aspect of analysis is defining the boundaries of the system and </div><div>determining whether or not a candidate system should consider other related systems. During analysis, data are collected on the available files, decision points, and transactions handled by the present system. Once analysis is completed the analyst has a firm understanding of what is to be </div><div>done. The next step is to decide how the problem might be solved. Thus, in systems, design we move from the logical to the physical aspects of the life cycle. <br><a href="http://www.ddegjust.ac.in/studymaterial/mca-3/ms-04.pdf">http://www.ddegjust.ac.in/studymaterial/mca-3/ms-04.pdf</a></div><ol><li>Analysis of a system’s user needs</li></ol><div> </div><div>The information analyst determines the needs of the user and the information flow that will satisfy those needs. The usual approach is to ask the user what information is currently available and what other information is required. Interaction between the analyst and the user usually leads to an agreement about what information will be provided by the candidate system.</div><ol><li>Information gathering techniques</li></ol><div><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting. <br><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants. <br><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action. <br><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks <br><br></div><ol><li>System’s analysis report</li></ol><div>The report should be as long as necessary to record fully (1) what was done by the project team, (2) what the team's findings are, and (3) what recommendations, including further courses of actions, are being made by the project team.  Main body of the report be reasonably concise, and that any and all additional details that are worth recording--whether for the sake of the historical record, or as bases for further work related to the project, or both--be placed in appendices, which are an admirable organizational device for this purpose.<br><a href="https://www.ischool.utexas.edu/~wyllys/SAEMaterials/stylesysanlrpt.html">https://www.ischool.utexas.edu/~wyllys/SAEMaterials/stylesysanlrpt.html</a></div><ol><li>Accountant role in systems analysis  </li></ol><div>First, accountants are users. Like all users, accountants must provide a clear picture of their problems and needs to the systems professional. For example, accountants must specify accounting techniques to be used; internal control requirements, such as audit trails; and special algorithms, such as depreciation models. <br><br></div><div>Second, accountants participate in systems development as members of the development team. Their involvement often extends beyond the development of strictly accounting information systems applications. Systems that do not process financial transactions may still draw on accounting data. The accountant may be consulted to provide advice or to determine if the proposed system constitutes an internal control risk. <br><br>Third, accountants are involved in systems development as auditors. Accounting information systems must be auditable. Some computer audit techniques require special features that must be designed into the system. The auditor/accountant has a stake in such systems and must be involved early in their design. <br><br></div><div><strong><br>System Design <br></strong><br></div><ol><li> User interface design</li></ol><div>User Interface (UI) Design focuses on anticipating what users might need to do and ensuring that the interface has elements that are easy to access, understand, and use to facilitate those actions. UI brings together concepts from <a href="https://www.usability.gov/what-and-why/interaction-design.html">interaction design</a>, <a href="https://www.usability.gov/what-and-why/visual-design.html">visual design</a>, and <a href="https://www.usability.gov/what-and-why/information-architecture.html">information architecture</a>.<br><a href="https://www.usability.gov/what-and-why/user-interface-design.html">https://www.usability.gov/what-and-why/user-interface-design.html</a></div><ol><li>Output design</li></ol><div> The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts. <br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a></div><ol><li>Input design</li></ol><div> In an information system, input is the raw data that is processed to produce output .<br><br></div><ol><li>Security and control measures </li></ol><div> The Security and Control Measures category encompasses the core activities directly related to protection and accounting of nuclear materials. It includes indicators of physical protection, control and accounting <br><a href="http://ntiindex.org/indicators/security-and-control-measures/">http://ntiindex.org/indicators/security-and-control-measures/</a></div><ol><li>Accountant role in systems designing </li></ol><div> The accountant plays an important role in the conceptual design of the system. He or she must recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood. <br><br></div><div><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:46:31 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248354001</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248354090</link>
         <description><![CDATA[<div><strong>System Analysis</strong></div><ol><li>Analysis of current system achievement</li><li>Analysis of a system’s user needs</li><li>Information gathering techniques</li><li>System’s analysis report</li><li>Accountant role in systems analysis </li></ol><div><strong><br>System Design <br></strong><br></div><ol><li> User interface design</li><li>Output design</li><li>Input design</li><li>Security and control measures </li><li>Accountant role in systems designing</li></ol>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:46:53 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248354090</guid>
      </item>
      <item>
         <title>AMINA BINTI RIDDUAN (Bb15110088)</title>
         <author>aminaridduan</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248354280</link>
         <description><![CDATA[<div><strong>System Analysis</strong><br>1. Analysis of current system achievement</div><div>- System analysis is a process of collecting and interpreting facts, identifying the problems, and decomposition of a system into its components. It is conducted for the purpose of studying a system or its parts in order to identify its objectives. It is a problem solving technique that improves the system and ensures that all the components of the system work efficiently to accomplish their purpose.<br> <a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_overview.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_overview.htm </a><br>2. Analysis of a system’s user needs<strong><br>-</strong>The information analyst determines the needs of the user and the information flow that will satisfy those needs. The usual approach is to ask the user what information is currently available and what other information is required. Interaction between the analyst and the user usually leads to an agreement about what information will be provided by the candidate system. <br>3. Information gathering technique</div><ul><li><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/"><mark>Brainstorming</mark></a>: This method used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.</li><li><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.</li><li><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>:  It is used in identifying problems and its underlying causes thus developing a preventive action.</li><li><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks. </li></ul><div><a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a><br><br></div><div>4. System’s analysis report<br> - Purpose of this report is to present the proposed system analysis for the client with the intention of ensuring all stakeholders involved agree on the planned solution. Throughout the project the analysis, development, implementation and testing phases will be conducted using, the industry standard, agile development life cycle. This specifies that changes can be made if required and appropriate. The system analysis report is intended for all the project's major stakeholders: the client, the academic supervisors and the development team.<br><a href="https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php">https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php</a> <strong><br></strong>5. Accountant role in systems analysis </div><div> -First is as an user.  Accountants must provide a clear picture of their problems and needs to the systems professional. <br>-Second as an auditor.  Accountant will help to require special features that must be designed into the system. <br> <a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a><em><br></em> <strong><br>System Design <br></strong>1.  User interface design</div><div> -A user interface is the part of the system with which the users interact. It includes the screen displays that provide navigation through the system, the screens and forms that capture data, and the reports that the system produces whether on paper, on the Web, or via some other media. </div><div><a href="https://www.safaribooksonline.com/library/view/system-analysis-and/9781118057629/18_chap09.html">https://www.safaribooksonline.com/library/view/system-analysis-and/9781118057629/18_chap09.html</a><br> <br>2. Output design<br>- The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.<br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br>3. Input design<br> - Input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR.<br> <a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm </a><br><br>4. Security and control measures <br>- Security and Control Measures category encompasses the core activities directly related to protection and accounting of nuclear materials. It includes indicators of physical protection, control and accounting, insider threat prevention, security during transport, response capabilities, and a new cyber security indicator. <br><a href="http://ntiindex.org/indicators/security-and-control-measures/">http://ntiindex.org/indicators/security-and-control-measures/</a><br>5. Accountant role in systems designing</div><div>- The accountant plays an important role in the conceptual design of the system. He or she must recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood. <br><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a></div><div><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:48:00 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248354280</guid>
      </item>
      <item>
         <title>NURFATIN AFIFAH BINTI ABDUL AZIZ (BB15110558)</title>
         <author>nurfatinafifahabdulaziz</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248354661</link>
         <description><![CDATA[<div><strong>System Analysis<br></strong><strong><em><mark>Analysis of current system</mark></em></strong><strong><em> </em></strong><strong><em><mark>achievement<br></mark></em></strong>Current systems analysis technique is used to evaluate the degree of support provided by current systems to the business activities of the enterprise. Assessments of user and technical satisfaction are performed and data, procedures and problems are analyzed. <br><em>Purpose</em><br>The purpose of current systems analysis technique is to identify shortcomings and issues with current systems. It is used to assess the usefulness, usability, and overall user satisfaction with the current systems to facilitate decision making concerning the current systems’ strategic and tactical viability.<br><em>Benefits</em><br>The current systems analysis technique provides a comprehensive and objective method for assessing current systems.<br><a href="https://www.projectmanagement.com/process/popup.cfm?ID=23401">https://www.projectmanagement.com/process/popup.cfm?ID=23401</a><br> <strong><em><br></em></strong><strong><em><mark>Analysis of a system’s user needs<br></mark></em></strong>Typical requirements gathering and analysis methods include:</div><ul><li><em>Surveys</em> – both open-ended and focused surveys, conducted electronically or on paper.</li><li><em>Interviews</em> – typically conducted face-to-face, but also over the telephone if deemed more appropriate.</li><li><em>Focus groups</em> – whilst being poorly suited to evaluating a product, focus groups are useful for discussing possible user requirements and brainstorming ideas.</li><li><em>Field studies </em>– observing the end-user situation and the environment in which a new product or system will be used is often extremely useful in understanding user needs.</li><li><em>Evaluation of an existing product</em> – provides a range of useful information (even competitor products can be tested). Usability evaluation reveals and clarifies good and bad aspects of current solutions - valuable input to new design work.</li><li><em>Task analysis</em> – a deeper analysis of users work with a system, useful for analysing how user's work tasks should be supported by functionality in a system.</li><li><em>User personas and usage scenarios</em> – concrete and illustrative data about typical users, their characteristics, usage situation, tasks and goals. Particularly useful in supporting early user interface design work.</li><li><em>Formulation of usability goals and overall design criteria</em> – help focus and steer the design process, supporting the evaluation of early concepts, prototypes and final designs.</li></ul><div><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a></div><div><strong><em><br></em></strong><strong><em><mark>Information gathering techniques</mark></em></strong></div><div>Information gathering includes various techniques like brainstorming, Delphi technique, interviews and root cause analysis. The ultimate aim of all these techniques is to identify and prepare a comprehensive list of risks in the project.</div><div><strong>Brainstorming: </strong>It is one of the most widely used techniques to identify risks in a project. Project team usually performs brainstorming, often with subject matter experts, risk management experts and other important stakeholders who can contribute to the risk identification. It allows people to come up with risks. During brainstorming sessions there should be no criticism of ideas. The main focus is to open up possibilities of risk.<br><strong>Delphi technique:</strong> This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.<br><strong>Root cause analysis:</strong> One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.<br><strong>Interviewing</strong>: Stakeholders, participants, and experts are interviewed to identify risks.&nbsp;</div><div><a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a><br><br><strong><em><mark>System’s analysis report</mark></em></strong></div><div>The report should be as long as necessary to record fully <em>(1) what was done by the project team, (2) what the team's findings are, and (3) what recommendations, including further courses of actions, are being made by the project team.&nbsp;</em></div><div><br></div><div>The report should use what is called "legal numbering". The report should use single spacing within paragraphs and a single-line space between paragraphs. Paragraphs should begin flush left; i.e., they should not begin with a tab indentation. All paragraphs and all headings, whether of sections, subsections, sub-subsections, or sub-sub-subsections (and lower-level sections), should be set flush left. Do not uses flush-right (also called "full") justification; ragged right margins actually make for easier and faster reading.&nbsp;<br><br></div><div>Figures and Tables are to take their numbers sequentially within the top-level section containing them. Make every effort to design Figures and Tables so that they fit onto the page in portrait, rather than landscape, orientation.&nbsp;<br><br></div><div>References are to be shown in what the <em>The Chicago Manual of Style</em> calls the "Author-Date Text Citations" style.&nbsp; For details, see that widely available manual.&nbsp;<br><br></div><div>Endnotes should be used rather than footnotes. The report is to be prepared using the Times New Roman font in size 10. Use 1-inch margins on top, bottom, left, and right of the text. Portions of the report that are prepared in a spreadsheet should be presented in portrait orientation and should use the Arial font in size 9. Page numbers should be placed at the bottom center of pages. Use single spacing for lines within paragraphs; use a single blank line to separate paragraphs. Be sure to use a spelling-check program or module on the report.&nbsp;<br><br></div><div>The report must begin with an Executive Summary, which must not exceed two pages in length. For the main body of the report, page numbering begins with 1 on the first page of the Executive Summary and runs sequentially till the end of the main body. Page numbers within appendices begin with 1 at the beginning of each appendix and have the style A-1, A-2, B-1.The pages containing the Table of Contents are numbered in lower-case Roman numerals: i, ii, iii. The Title Page and Copyright Page have no numbers.&nbsp;<br><br></div><div>The styling of headings of sections, subsections, etc., is shown in the following example. Note that the text of the sub-sub-subsection level begins on the same line as the heading, instead in a new paragraph as with the higher levels. No heading ends with a period unless it is a sub-sub-subsection heading.&nbsp;</div><div><a href="https://www.ischool.utexas.edu/~wyllys/SAEMaterials/stylesysanlrpt.html">https://www.ischool.utexas.edu/~wyllys/SAEMaterials/stylesysanlrpt.html</a><br><strong><em><mark><br>Accountant role in systems analysis&nbsp;</mark></em></strong></div><div>First, accountants are <em>users</em>. All systems that process financial transactions impact the accounting function in some way. Accountants must provide a clear picture of their problems and needs to the systems professional. For example, accountants must specify accounting techniques to be used; internal control requirements, such as audit trails.<br><br></div><div>Second,&nbsp; as <em>members of the development team.</em> Their involvement often extends beyond the development of strictly accounting information systems applications. Systems that do not process financial transactions may still draw on accounting data. The accountant may be consulted to provide advice or to determine if the proposed system constitutes an internal control risk.<br><br></div><div>Third, accountants are involved&nbsp; as auditors. Accounting information systems must be auditable. Some computer audit techniques require special features that must be designed into the system.</div><div><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a><strong><br><br>System Design <br></strong><strong><em><mark>User interface design<br></mark></em></strong>User interface design or UI design generally refers to the visual layout of the elements that a user might interact with in a website, or technological product. This could be the control buttons of a radio, or the visual layout of a webpage. User interface designs must not only be attractive to potential users, but must also be functional and created with users in mind.<br><a href="https://pidoco.com/en/help/ux/user-interface-design">https://pidoco.com/en/help/ux/user-interface-design</a><br><strong><em><mark><br>Output design<br></mark></em></strong>The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.</div><div><br>Objectives of Output Design</div><div>The objectives of input design are&nbsp;</div><ul><li>To develop output design that serves the intended purpose and eliminates the production of unwanted output.</li><li>To develop the output design that meets the end users requirements.</li><li>To deliver the appropriate quantity of output</li><li>To form the output in appropriate format and direct it to the right person.</li><li>To make the output available on time for making good decisions.</li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm&nbsp;</a></div><div><br><strong><em><mark>Input design<br></mark></em></strong>In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR.</div><div>The objectives of input design are:</div><ul><li>To design data entry and input procedures</li><li>To reduce input volume</li><li>To design source documents for data capture or devise other data capture methods</li><li>To design input data records, data entry screens, user interface screens, etc.</li><li>To use validation checks and develop effective input controls.&nbsp;</li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a></div><div><strong><em><mark>Security and control measures <br></mark></em></strong>&nbsp;</div><div>Security- System security refers to protecting the system from theft, unauthorized access and modifications, and accidental or unintentional damage. In computerized systems, security involves protecting all the parts of computer system which includes data, software, and hardware. Systems security includes system privacy and system integrity.</div><ul><li><strong>System privacy</strong> deals with protecting individuals systems from being accessed and used without the permission/knowledge of the concerned individuals.</li><li><strong>System integrity</strong> is concerned with the quality and reliability of raw as well as processed data in the system.</li></ul><div><br>Control Measures- There are variety of control measures which can be broadly classified as follows :<br>Backup</div><ul><li>Regular backup of databases daily/weekly depending on the time criticality and size.</li><li>Incremental back up at shorter intervals.</li><li>Backup copies kept in safe remote location particularly necessary for disaster recovery.</li><li>Duplicate systems run and all transactions mirrored if it is a very critical system and cannot tolerate any disruption before storing in disk.<br><br></li></ul><div>Physical Access Control to Facilities</div><ul><li>Physical locks and Biometric authentication. For example, finger print</li><li>ID cards or entry passes being checked by security staff.</li><li>Identification of all persons who read or modify data and logging it in a file.</li></ul><div><br>Using Logical or Software Control</div><ul><li>Password system.</li><li>Encrypting sensitive data/programs.</li><li>Training employees on data care/handling and security.</li><li>Antivirus software and Firewall protection while connected to internet.&nbsp;</li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm</a><br><strong><em><mark><br>Accountant role in systems Designing</mark></em></strong></div><div>The accountant plays an important role in the conceptual design of the system. He or she must recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood. These issues need not be specified in detail at this point, but they should be recognized as items to be addressed during the construct phase of the system. Furthermore, the auditability of a system depends in part on its design characteristics. Some computer auditing techniques require systems to be designed with built-in audit features. Such features require resources and need to be considered at conceptual design.<strong><br></strong><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/"><strong>http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</strong></a><strong><br></strong><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:51:01 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248354661</guid>
      </item>
      <item>
         <title>ASMAUL HUSNA BINTI NURDIN BB15110106</title>
         <author>bb15110106</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248354791</link>
         <description><![CDATA[<div><br><br>ecture 5:</div><div>undefined</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:51:52 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248354791</guid>
      </item>
      <item>
         <title>ASMAUL HUSNA BINTI NURDIN </title>
         <author>bb15110106</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248354792</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:51:52 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248354792</guid>
      </item>
      <item>
         <title>ASMAUL HUSNA BINTI NURDIN BB151101</title>
         <author>bb15110106</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248354793</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:51:52 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248354793</guid>
      </item>
      <item>
         <title>MARIYANI BINTI SIDIRMAN (BB15110371)</title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248354903</link>
         <description><![CDATA[<div><br><strong>System Analysis<br></strong>1. Analysis of current system achievement<br>Systems analysis is a problem-solving method that involves looking at the wider system, breaking apart the parts, and figuring out how it works in order to achieve a particular goal. System analysis will improved performance and a feeling of achievement with quality information </div><div><a href="https://study.com/academy/lesson/systems-analysis-definition-example.html">https://study.com/academy/lesson/systems-analysis-definition-example.html</a><br> </div><div><a href="http://www.ddegjust.ac.in/studymaterial/mca-3/ms-04.pdf">http://www.ddegjust.ac.in/studymaterial/mca-3/ms-04.pdf</a> </div><div><br></div><div>2. Analysis of system's user needs<br><br>The developer of the system must concern about the user's needs .This is due:</div><ul><li>Poorly specified user requirements are one of the most significant factors behind IT project failure.</li><li>A successful product or system requires a proper understanding of both user and organisational requirements - we help integrate and balance the two in the specification process.</li><li>Avoid over-reliance on internally generated requirements (what its believed that users want), as opposed to data from end-user requirements studies (what users actually need).</li><li>Usability Partners support development projects, bringing key user data into the design process and analysing user needs, their work practice, and the situations in which they work.</li></ul><div><br><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a><br><br><br>3. Information gathering techniques</div><ul><li><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. </li><li><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.</li><li><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: It is used in identifying problems and its underlying causes thus developing a preventive action.</li><li><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks. </li></ul><div><a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a><br><br>4. System's analysis report<br> System's analysis report is a summarizes and documents where the findings of analysis activities and serves as a repository of data from which system designers can draw.</div><div><a href="https://quizlet.com/10197074/ais-introduction-to-systems-development-and-systems-analysis-flash-cards/">https://quizlet.com/10197074/ais-introduction-to-systems-development-and-systems-analysis-flash-cards/</a><br><br>5. Accountant role in system analysis<br>First is as an a user.  accountants must provide a clear picture of their problems and needs to the systems professional. <br>Second as an auditor.  Accountant will help to require special features that must be designed into the system. <br><br><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc</a></div><div><br><strong>System Design<br></strong>1. User interface design<br>User interface design is the design of user interfaces for software or machines, such as the look of a mobile app, with a focus on <em>ease of use</em> and <em>pleasurability</em> for the user. It is usually refers to the design of graphical user interfaces—but can also refer to others, such as natural and voice user interfaces. In other words, user interface design is a display featured of the system<br><a href="https://www.interaction-design.org/literature/topics/ui-design">https://www.interaction-design.org/literature/topics/ui-design</a><br><br>2. Output design<br>The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts. <br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br>3. Input design<strong><br></strong>In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc. <strong><br><br></strong>4. Security and control measures<br><strong>System security</strong> refers to protecting the system from theft, unauthorized access and modifications, and accidental or unintentional damage. In computerized systems, security involves protecting all the parts of computer system which includes data, software, and hardware. Systems security includes system privacy and system integrity.</div><ul><li><strong>System privacy</strong> deals with protecting individuals systems from being accessed and used without the permission/knowledge of the concerned individuals.</li><li><strong>System integrity</strong> is concerned with the quality and reliability of raw as well as processed data in the system.</li></ul><div><strong>Control Measures<br></strong>a)<strong> </strong>Backup<br>b) Physical Access Control to Facilities<br>c) Using Logical or Software Control<br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm</a><br><br></div><div>5.  Accountant role in system designing<br>Accountants are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument. This function of designing AIS includes the design of managerial accounting information system to aid management in decision making processes. <br><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:52:41 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248354903</guid>
      </item>
      <item>
         <title>NURUL HIDAYAH BINTI ABDUL SUHUD BB15110588</title>
         <author>nurulhidayah160596</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248355050</link>
         <description><![CDATA[<div><strong>System Analysis<br>1. </strong>Analysis of current system achievement</div><div>- System analysis is the process of studying a procedure or business in order to identify its goals and purposes and create systems and procedures that will achieve them in an efficient way <br>-&nbsp; The subject of current systems analysis is usually greeted with dismay or disdain by systems departments. There are many reasons for this. In many installations, the support of current systems takes more than 85% of the systems department's time, and the departments are more than ready to get on with new systems development and bury the old, non-working systems as quickly as possible. In cases where systems do not require a lot of maintenance, the systems department may find that the current systems are not giving management the kind of information it needs for effective decision making; these current systems become likely candidates for replacement.<br><a href="https://en.wikipedia.org/wiki/Systems_analysis">https://en.wikipedia.org/wiki/Systems_analysis</a><br><a href="http://www.modernanalyst.com/Resources/Articles/tabid/115/ID/458/Current-Systems-Analysis.aspx">http://www.modernanalyst.com/Resources/Articles/tabid/115/ID/458/Current-Systems-Analysis.aspx</a><br><br></div><div>2. Analysis of a system’s user needs<br>There are several way to know about the system's user needs which is understand their needs :</div><ul><li>Poorly specified user requirements are one of the most significant factors behind IT project failure.</li><li>A successful product or system requires a proper understanding of both user and organisational requirements - we help integrate and balance the two in the specification process.</li><li>Avoid over-reliance on internally generated requirements (what its believed that users want), as opposed to data from end-user requirements studies (what users actually need).</li><li>Usability Partners support development projects, bringing key user data into the design process and analysing user needs, their work practice, and the situations in which they work.&nbsp;</li></ul><div>Below are the way on how to analyze the system's user needs:</div><ul><li><em>Surveys</em> – both open-ended and focused surveys, conducted electronically or on paper.</li><li><em>Interviews</em> – typically conducted face-to-face, but also over the telephone if deemed more appropriate.</li><li><em>Focus groups</em> – whilst being poorly suited to evaluating a product, focus groups are useful for discussing possible user requirements and brainstorming ideas.</li><li><em>Field studies </em>– observing the end-user situation and the environment in which a new product or system will be used is often extremely useful in understanding user needs.</li><li><em>Evaluation of an existing product</em> – provides a range of useful information (even competitor products can be tested). Usability evaluation reveals and clarifies good and bad aspects of current solutions - valuable input to new design work.</li><li><em>Task analysis</em> – a deeper analysis of users work with a system, useful for analysing how user's work tasks should be supported by functionality in a system.</li><li><em>User personas and usage scenarios</em> – concrete and illustrative data about typical users, their characteristics, usage situation, tasks and goals. Particularly useful in supporting early user interface design work.</li><li><em>Formulation of usability goals and overall design criteria</em> – help focus and steer the design process, supporting the evaluation of early concepts, prototypes and final designs.&nbsp;</li></ul><div><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a></div><div>3. Information gathering techniques<br>-&nbsp; Information Gathering is a very key part of the feasibility analysis process. Information gathering is both an art and a science. It is a science because it requires a proper methodology and tools in order to be effective. It is an art too, because it requires a sort of mental dexterity to achieve the best results. The information gathering techniques are include interviewing, surveys, workshops which is refer to features and the system uses, and prototyping.<br>4. System's analysis report<br>-&nbsp; The System Analysis Report also includes the System Health Score(1) which indicates the health of the system based upon a comparison of specific criteria relative to other systems subscribed to Guardian Support on a global basis. The System Health Score included in this report is based on the status of the system at the end of this reporting period. Scores are recorded on a weekly basis, and the highest score of the month is included in the trend. <br><a href="http://www.emerson.com/documents/automation/guardian-sample-system-analysis-report-en-67944.pdf">http://www.emerson.com/documents/automation/guardian-sample-system-analysis-report-en-67944.pdf</a></div><div>5. Accountant role in systems analysis&nbsp;</div><div><strong><br>System Design&nbsp;<br></strong><br></div><ol><li>&nbsp;User interface design</li></ol><div>-&nbsp; <strong>User interface design</strong> (<strong>UI</strong>) or <strong>user interface engineering</strong> is the design of user interfaces for machines and software, such as computers, home appliances, mobile devices, and other electronic devices, with the focus on maximizing usability and the user experience. The goal of user interface design is to make the user's interaction as simple and efficient as possible, in terms of accomplishing user goals (user-centered design).<br>- Good user interface design facilitates finishing the task at hand without drawing unnecessary attention to itself. Graphic design and typography are utilized to support its usability, influencing how the user performs certain interactions and improving the aesthetic appeal of the design; design aesthetics may enhance or detract from the ability of users to use the functions of the interface.<sup>[1]</sup> The design process must balance technical functionality and visual elements (e.g., mental model) to create a system that is not only operational but also usable and adaptable to changing user needs.&nbsp;<br>2. Output design<br>- &nbsp;</div><div>The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.<br>- Objectives of Output Design</div><ul><li>To develop output design that serves the intended purpose and eliminates the production of unwanted output.<br><br></li><li>To develop the output design that meets the end users requirements.<br><br></li><li>To deliver the appropriate quantity of output.<br><br></li><li>To form the output in appropriate format and direct it to the right person.<br><br></li><li>To make the output available on time for making good decisions.&nbsp;</li></ul><div>3. Input design<br>-&nbsp; In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.<br><br></div><div>Therefore, the quality of system input determines the quality of system output. Welldesigned input forms and screens have following properties −<br><br></div><ul><li>It should serve specific purpose effectively such as storing, recording, and retrieving the information.<br><br></li><li>It ensures proper completion with accuracy.<br><br></li><li>It should be easy to fill and straightforward.<br><br></li><li>It should focus on user’s attention, consistency, and simplicity.<br><br></li><li>All these objectives are obtained using the knowledge of basic design principles regarding −<br><br><ul><li>What are the inputs needed for the system?<br><br></li><li>How end users respond to different elements of forms and screens.<br><br></li></ul></li></ul><div>- The objectives of input design are&nbsp;<br><br></div><ul><li>To design data entry and input procedures<br><br></li><li>To reduce input volume<br><br></li><li>To design source documents for data capture or devise other data capture methods<br><br></li><li>To design input data records, data entry screens, user interface screens, etc.<br><br></li><li>To use validation checks and develop effective input controls.&nbsp;<br><br></li></ul><div>4. Security and control measures <br>&nbsp;- <strong>Security controls</strong> are safeguards or countermeasures to avoid, detect, counteract, or minimize security risks to physical property, information, computer systems, or other assets.<br>- They can be classified by several criteria. For example, according to the time that they act, relative to a security incident:<br><br></div><ul><li>Before the event, <strong>preventive controls</strong> are intended to prevent an incident from occurring e.g. by locking out unauthorized intruders;</li><li>During the event, <strong>detective controls</strong> are intended to identify and characterize an incident in progress e.g. by sounding the intruder alarm and alerting the security guards or police;</li><li>After the event, <strong>corrective controls</strong> are intended to limit the extent of any damage caused by the incident e.g. by recovering the organization to normal working status as efficiently as possible. &nbsp;</li></ul><div>5. Accountant role in systems designing</div><div><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:53:56 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248355050</guid>
      </item>
      <item>
         <title>ROSITA BINTI DARWIS (BB15110639)</title>
         <author>bb15110639</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248355052</link>
         <description><![CDATA[<div><strong>System Analysis</strong></div><ol><li><strong>Analysis of current system achievement :&nbsp;</strong>Systems analysis is the process of observing systems for troubleshooting or development purposes. it is applied to information technology, where computer-based systems require defined analysis according to their makeup and design. </li><li><strong>Analysis system’s user needs :</strong> It is often used across many industries such as software development, automobiles, consume products and banking services. Needs analysis was originally used for software developers, who used the system in tandem with requirements analysis.&nbsp;</li><li><strong>Information gathering techniques :</strong> There are few types of information techniques gathering such as brainstorming, Delphi technique, root cause analysis, interviewing. <a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a></li><li><strong>System’s analysis report : </strong>The event that marks the conclusion of the systems analysis phase is the preparation of a formal systems analysis report. This report presents management of the steering committee with the survey findings, the problems identified with the current system, the user's needs, and the requirements of the new system.&nbsp;</li><li><strong>Accountant role in systems analysis : </strong>Accountants are involved in the system development since information systems represent a significant financial transaction that consumes both financial and human resources. The accountants are concerned with these projects since they have significant financial resource implications. <a href="https://www.coursehero.com/file/p3dmqhn/3-What-is-the-role-of-the-accountant-in-the-SDLC-Why-might-the-accountants-be/">https://www.coursehero.com/file/p3dmqhn/3-What-is-the-role-of-the-accountant-in-the-SDLC-Why-might-the-accountants-be/</a></li></ol><div><strong><br>System Design&nbsp;<br></strong><br></div><ol><li><strong>&nbsp;User interface design: </strong>User interfaces should be designed to match the skills, experience and expectations of its anticipated users. User interface design must take account of the needs, experience and capabilities of the system users and its principles should underlies interface designs although not all principles are applicable to all designs. <a href="https://ifs.host.cs.st-andrews.ac.uk/Books/SE7/Presentations/PDF/ch16.pdf">https://ifs.host.cs.st-andrews.ac.uk/Books/SE7/Presentations/PDF/ch16.pdf</a></li><li><strong>Output design: </strong>Its objectives is to design output to serve the intended purpose. This means the system's objectives should be met but the needs to linked to the business tactics. Its also used to design the output to fit the user. Next, delivering the appropriate quantity of output. Besides making sure the output is where it is needed.&nbsp;</li><li><strong>Input design: </strong>It is the process of converting a user-oriented description of the input into&nbsp; computer-based system. This design is important to avoid errors in the data input process and show the correct direction to the management for getting correct information from the computerized system.&nbsp; <a href="https://www.slideshare.net/madhukarreddy007/input-and-output-design">https://www.slideshare.net/madhukarreddy007/input-and-output-design&nbsp;</a></li><li><strong>Security and control measures: </strong>The controls for computerized accounting information system is refer to measures or techniques that prevent, detect, and correct conditions that may lead to loss or damage to the business firm and computer controls can be classified as general controls and application controls.&nbsp;</li><li><strong>Accountant role in systems designing: </strong>Accountant also be known as the system designers. Accountant are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. This function of designing AIS includes the design of managerial accounting information system to aid management in decision making processes.&nbsp;</li></ol>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:53:58 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248355052</guid>
      </item>
      <item>
         <title>NORATNA BINTI AWANG ASAL (BB15110493)</title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248355185</link>
         <description><![CDATA[<div><strong>System Analysis</strong> <br><mark>1. Analysis of current system achievement<br></mark>Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. A key question is, what must be done to solve the problem? One aspect of analysis is defining the boundaries of the system and determining whether or not a candidate system should consider other related systems. During analysis, data are collected on the available files, decision points, and transactions handled by the present system. Data flow diagrams interviews, on – site observations, and questionnaires are examples of the analysis tools. The interviews is a commonly used tool in analysis, it requires special skills and sensitivity to the subjects being interviewed.<br><a href="http://www.w3computing.com/systemsanalysis/analyzing-system-needs-sdlc/">http://www.w3computing.com/systemsanalysis/analyzing-system-needs-sdlc/</a><mark><br></mark><br><mark>2. Analysis of a system’s user needs<br></mark>Understanding user requirements is an integral part of information systems design and is critical to the success of interactive systems. It is now widely understood that successful systems and products begin with an understanding of the needs and requirements of the users. As specified in the ISO 13407 standard (ISO, 1999), user-centred design begins with a thorough understanding of the needs and requirements of the users. The benefits can include increased productivity, enhanced quality of work, reductions in support and training costs, and improved user satisfaction. Requirements analysis is not a simple process. Particular problems faced by the analyst are:<br>&nbsp;• addressing complex organisational situations with many stakeholders<br>&nbsp;• users and designers thinking along traditional lines, reflecting the current system and processes, rather than being innovative<br>&nbsp;• users not knowing in advance what they want from the future system (Olphert &amp; Damodaran, 2002) 2 M. Maguire and N. Bevan<br>&nbsp;• rapid development cycles, reducing the time available for user needs analysis <br>• representing user requirements in an appropriate form<br><a href="http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89.2102&amp;rep=rep1&amp;type=pdf">http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89.2102&amp;rep=rep1&amp;type=pdf</a><br><mark>3. Information gathering techniques<br></mark>Managing information involves gathering and distributing necessary information and assimilating them on the project management activities and processes. The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:<br><br></div><ul><li><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.</li><li><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.</li><li><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.</li><li><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks.</li></ul><div><br></div><div><br><mark>4. System’s analysis report</mark><br>The report should be as long as necessary to record fully (1) what was done by the project team, (2) what the team's findings are, and (3) what recommendations, including further courses of actions, are being made by the project team.<br><a href="https://www.ischool.utexas.edu/~wyllys/SAEMaterials/stylesysanlrpt.html">https://www.ischool.utexas.edu/~wyllys/SAEMaterials/stylesysanlrpt.html</a><br>5. <mark>Accountant role in systems analysis <br></mark>&nbsp;</div><div>First, accountants are users. All systems that process financial transactions impact the accounting function in some way. Like all users, accountants must provide a clear picture of their problems and needs to the systems professional. For example, accountants must specify accounting techniques to be used; internal control requirements, such as audit trails; and special algorithms, such as depreciation models.<br><br></div><div>Second, accountants participate in systems development as members of the development team. Their involvement often extends beyond the development of strictly accounting information systems applications. Systems that do not process financial transactions may still draw on accounting data. The accountant may be consulted to provide advice or to determine if the proposed system constitutes an internal control risk.<br><br></div><div>Third, accountants are involved in systems development as auditors. Accounting information systems must be auditable. Some computer audit techniques require special features that must be designed into the system. The auditor/accountant has a stake in such systems and must be involved early in their design. <br><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a><strong><br>System Design <br></strong>1.<mark> User interface design</mark></div><div>User Interface (UI) Design focuses on anticipating what users might need to do and ensuring that the interface has elements that are easy to access, understand, and use to facilitate those actions. UI brings together concepts from <a href="https://www.usability.gov/what-and-why/interaction-design.html">interaction design</a>, <a href="https://www.usability.gov/what-and-why/visual-design.html">visual design</a>, and <a href="https://www.usability.gov/what-and-why/information-architecture.html">information architecture</a>.<br><mark>2.Output design<br></mark>The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.<br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><mark>3. Input design</mark><br>input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.<br>Therefore, the quality of system input determines the quality of system output. Well designed input forms and screens have following properties −<br><br></div><ul><li>It should serve specific purpose effectively such as storing, recording, and retrieving the information.<br><br></li><li>It ensures proper completion with accuracy.<br><br></li><li>It should be easy to fill and straightforward.<br><br></li><li>It should focus on user’s attention, consistency, and simplicity.<br><br></li><li>All these objectives are obtained using the knowledge of basic design principles regarding −<br><br><ul><li>What are the inputs needed for the system?<br><br></li><li>How end users respond to different elements of forms and screens.</li></ul></li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a></div><div><br><mark>4.Security and control measures<br></mark>&nbsp;The Security and Control Measures category encompasses the core activities directly related to protection and accounting of nuclear materials. It includes indicators of physical protection, control and accounting, insider threat prevention, security during transport, response capabilities, and a new cyber security indicator. <br><a href="http://ntiindex.org/indicators/security-and-control-measures/">http://ntiindex.org/indicators/security-and-control-measures/</a><br><mark>5. Accountant role in systems designing<br></mark>&nbsp;The accountant plays an important role in the conceptual design of the system. He or she must recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood. These issues need not be specified in detail at this point, but they should be recognized as items to be addressed during the construct phase of the system. Furthermore, the audibility of a system depends in part on its design characteristics. Some computer auditing techniques require systems to be designed with built-in audit features. Such features require resources and need to be considered at conceptual design.<br><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a></div><div><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:55:00 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248355185</guid>
      </item>
      <item>
         <title>ASMAUL HUSNA NURDIN BB15110106</title>
         <author>bb15110106</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248355219</link>
         <description><![CDATA[<div><strong>System Analysis<br></strong>&nbsp;System analysis, then, is the process of gathering and interpreting facts, diagnosing problems, and using the information to recommend improvements to the system. This is the job of the systems analyst.&nbsp;</div><ol><li><em><mark>Analysis of current system achievement</mark></em></li></ol><div>&nbsp;The system analyst gives a system development project meaning &amp; direction. A candidate system is approached after the analyst has a through understanding of user needs &amp; problems. A viable solution is worked out and then communicates the same. Candidate systems often cut across the boundaries of users in the organization. For example, a billing system may involve users in the sales order department, the credit department, the warehouse and the accounting department. To make sure that all users’ needs are met, a project from that represents each user works with the analysis to carry out a system development project.&nbsp;</div><div><em><mark>2. Analysis of a system’s user needs<br></mark></em>&nbsp;Evaluating an existing or competitor system is one of the user needs of a analysis system. it&nbsp; can provide valuable information about the extent to which current systems meet user needs and can identify potential usability problems to avoid in the new system. Useful features identified in a competitor system can also be fed into the design process as potential user requirements. Measures of effectiveness, efficiency and satisfaction can be used as a baseline for the new system. To obtain accurate measures a controlled user test should be used, but valuable information can still be obtained from less formal methods of testing. <br><br><em><mark>3. Information gathering techniques<br>-</mark></em> Management Information Systems (MIS) <em><mark><br>-</mark></em> Computer – Based Information Systems <br><mark>-</mark> Decision Support Systems (DSS) <br><br><em><mark>4. System’s analysis report<br></mark></em><br></div><ol><li>Accountant role in systems analysis&nbsp;</li></ol><div>&nbsp;<figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:194,&quot;url&quot;:null,&quot;width&quot;:259}" data-trix-content-type="image"><img src="null" width="259" height="194"><figcaption class="attachment__caption"></figcaption></figure>&nbsp;</div><div><strong><br>System Design ---</strong> System design is the process of planning a new business system or one to replace or complement an existing system. But before this planning can be done, we must thoroughly understand the old system and determine how computers can best be used to make its operation more effective. <strong><br></strong><br></div><ol><li>&nbsp;User interface design</li></ol><div><em><mark>&nbsp;User interface design (UI) or user interfaceengineering is the design of user interfaces for machines and software, such as computers, home appliances, mobile devices, and other electronic devices, with the focus on maximizing usability and the user experience.&nbsp;</mark></em></div><div><br>2. Output design<br>&nbsp;<mark>OUTPUT DESIGN A quality output is one, which meets the requirements of the end user and presents the information clearly. In any system results of processing are communicated to the users and to other system through outputs. It Create document, report, or other formats that contain information produced by the</mark> <strong><mark>system. <br></mark></strong><a href="https://www.slideshare.net/madhukarreddy007/input-and-output-design"><strong><mark>https://www.slideshare.net/madhukarreddy007/input-and-output-design</mark></strong></a><strong><mark><br><br></mark></strong><strong>3. Input design<br></strong>&nbsp;<figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:194,&quot;url&quot;:&quot;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcReCtGWLUhc-tXeJrGmuPNpsAl-oBimfJRwiOiOCr4AkqvcpFeU&quot;,&quot;width&quot;:259}" data-trix-content-type="image"><img src="https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcReCtGWLUhc-tXeJrGmuPNpsAl-oBimfJRwiOiOCr4AkqvcpFeU" width="259" height="194"><figcaption class="attachment__caption"></figcaption></figure> 4. Security and control measures <br><figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:194,&quot;url&quot;:&quot;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQaaEpQWCte7844vnAWtRl-fngArH6GJvFALaQ48q2IAQVfy3toVA&quot;,&quot;width&quot;:259}" data-trix-content-type="image"><img src="https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQaaEpQWCte7844vnAWtRl-fngArH6GJvFALaQ48q2IAQVfy3toVA" width="259" height="194"><figcaption class="attachment__caption"></figcaption></figure> 5. Accountant role in systems designing<br><br><em><mark>&nbsp;The accountant while being involved in the implementation process of the AIS may discover an implementation problem that non accountants may find difficult communicating back to the systems designers. <br></mark></em>&nbsp;<figure class="attachment attachment--preview" data-trix-attachment="{&quot;contentType&quot;:&quot;image&quot;,&quot;height&quot;:194,&quot;url&quot;:&quot;https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcSqr107Zit5-H-Cbe4kgs4NrJlqU1PW8VXRY1GNBdDI3aO7N1RgDA&quot;,&quot;width&quot;:259}" data-trix-content-type="image"><img src="https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcSqr107Zit5-H-Cbe4kgs4NrJlqU1PW8VXRY1GNBdDI3aO7N1RgDA" width="259" height="194"><figcaption class="attachment__caption"></figcaption></figure><em><mark><br></mark></em><br></div><div><br></div><div><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:55:17 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248355219</guid>
      </item>
      <item>
         <title>SUHAILAH BINTI JALIL (BB15110725)</title>
         <author>suhailahjalil1493</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248355465</link>
         <description><![CDATA[<div><br></div><div><strong>System Analysis<br></strong><br></div><pre><strong>Analysis of current system achievement</strong></pre><div> </div><div>According to current definitions, systems analysis is a combination of procedures and analytical methods used for the study of ill-structured problems. The concept of <em>systems analysis</em> is broader than that of <em>decision making</em>, including also procedures of problem investigation known as a “systems approach”. The systems approach is a train of logical stages: definition of a goal or a set of goals; identification of alternative ways of goal achievement; construction of the model presenting the interdependence of goals, means and parameters of the system; determination of the decision rule for selecting the preferred alternative.<br><br></div><blockquote>Thus, we may define systems analysis as a combination of the general framework of the systems approach with decision making tools. The last stage is in fact that commonly known as decision making. However, in earlier versions of systems analysis only a “cost-effectiveness” criterion was usually applied in the decision rule. </blockquote><div><br><br><br><strong>Analysis of a system’s user needs</strong></div><div>Requirements analysis is not a simple process. Particular problems faced by the analyst are: </div><ul><li>addressing complex organisational situations with many stakeholders</li><li> users and designers thinking along traditional lines, reflecting the current system and processes, rather than being innovative </li><li>users not knowing in advance what they want from the future system</li><li>rapid development cycles, reducing the time available for user needs analysis </li><li> representing user requirements in an appropriate form.  </li></ul><div><a href="http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89.2102&amp;rep=rep1&amp;type=pdf">http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89.2102&amp;rep=rep1&amp;type=pdf</a></div><div><br></div><div><strong>Information gathering techniques<br></strong> </div><div><mark>Existing documents</mark> e.g. </div><ul><li>Organization charts </li><li>Policy manuals </li><li>Procedural manuals </li><li>Job descriptions </li><li>Forms, reports </li><li>Document flow and work flow diagrams</li></ul><div><mark>Systems flow charts </mark><br><mark>If computerized</mark> </div><ul><li>Computer program documentation </li><li>Data dictionary listings </li><li>Computer operation manuals  </li></ul><div><mark> System users and managers</mark> </div><div><br><mark>External sources</mark>: Might be necessary especially when examining alternatives for the new systems. To see what is available </div><ul><li>Other companies </li><li>Equipment and software vendors </li><li>Business publications, seminars, workshops, or visits to show rooms, exhibitions, or other companies for demonstrations. </li></ul><div><br></div><blockquote><em>The existing systems must be understood before they can be comprehensively designed.  The best way of understanding the activities that take place in any particular system whether computerized or manual is to get information from the users and other processing areas </em></blockquote><div><strong><br><br>System’s analysis report<br></strong>The report should be as long as necessary to record fully </div><ol><li>what was done by the project team, </li><li> what the team's findings are, and </li><li>what recommendations, including further courses of actions, are being made by the project team. </li></ol><div><br>The report should use what is called "legal numbering". That is, the main sections of the report should have numbers like 1, 2, etc. <br><br>The report should use single spacing within paragraphs and a single-line space between paragraphs. Paragraphs should begin flush left; i.e., they should not begin with a tab indentation. <br><a href="https://www.ischool.utexas.edu/~wyllys/SAEMaterials/stylesysanlrpt.html">https://www.ischool.utexas.edu/~wyllys/SAEMaterials/stylesysanlrpt.html</a><br><br></div><div><strong>Accountant role in systems analysis <br></strong> </div><div>Like all users, accountants must provide a clear picture of their problems and needs and analysis to the systems professional. For example, accountants must specify accounting techniques to be used; internal control requirements, such as audit trails; and special algorithms, such as depreciation models.<br><br></div><div>Second, accountants participate in systems analysis as members of the development team. Their involvement often extends beyond the development of strictly accounting information systems applications. Systems that do not process financial transactions may still draw on accounting data. The accountant may be consulted to provide advice or to determine if the proposed system constitutes an internal control risk.<br><br></div><div>Third, accountants are involved in systems analysis as auditors. Accounting information systems must be auditable. Some computer audit techniques require special features that must be designed into the system. The auditor/accountant has a stake in such systems and must be involved early in their design. <br><br></div><div><strong>System Design <br><br> User interface design<br></strong><br></div><div>A user interface is the part of the system with which the users interact. It includes the screen displays that provide navigation through the system, the screens and forms that capture data, and the reports that the system produces (whether on paper, on the Web, or via some other media) <br> </div><div><mark>Principles for User Interface Design</mark></div><ul><li><em>Layout</em></li><li><em>Content Awareness</em></li><li><em>Aesthetics</em></li><li><em>User Experience</em></li><li><em>Consistency</em></li><li><em>Minimize User Effort</em></li></ul><div><br><mark>User Interface Design Process</mark></div><ul><li><em>Use Scenario Development</em></li><li><em>Interface Structure Design</em></li><li><em>Interface Standards Design</em></li><li><em>Interface Design Prototyping</em></li><li><em>Interface Evaluation</em> </li></ul><div><a href="https://www.safaribooksonline.com/library/view/system-analysis-and/9781118057629/18_chap09.html">https://www.safaribooksonline.com/library/view/system-analysis-and/9781118057629/18_chap09.html</a></div><div><br><strong>Output design<br></strong>The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts. <br> </div><div><mark>The objectives of input design are </mark></div><ul><li>To develop output design that serves the intended purpose and eliminates the production of unwanted output.</li><li>To develop the output design that meets the end users requirements.</li><li>To deliver the appropriate quantity of output.</li><li>To form the output in appropriate format and direct it to the right person.</li><li>To make the output available on time for making good decisions. </li></ul><div><strong>Input design<br></strong> In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.<br><br></div><div>Therefore, the quality of system input determines the quality of system output. Welldesigned input forms and screens have following properties −</div><ul><li>It should serve specific purpose effectively such as storing, recording, and retrieving the information.</li><li>It ensures proper completion with accuracy.</li><li>It should be easy to fill and straightforward.</li><li>It should focus on user’s attention, consistency, and simplicity.</li><li>All these objectives are obtained using the knowledge of basic design principles regarding −<ul><li><em>What are the inputs needed for the system?</em></li><li><em>How end users respond to different elements of forms and screens. </em></li></ul></li></ul><div><strong>Security and control measures<br></strong>Importance of security the</div><div>gravity of the systems security</div><div>issue is reflected in widely known studies of computer</div><div>abuse. <br><br>It is very important to ensure the reliability of reports produced by an information system</div><ul><li> If unreliability is seen by users the entire credibility of the system is lost </li><li> Ensuring reliability is not difficult for small systems but when a system has to handle massive data it is a challenge </li><li> Systematic controls are thus essential when a system is designed </li></ul><div><br></div><div><strong> Accountant role in systems designing <br></strong><br></div><blockquote>Accountant are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument<br><br></blockquote>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 02:57:21 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248355465</guid>
      </item>
      <item>
         <title>NG SYIE NIE (BB14110434</title>
         <author>ngsyienie</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248355879</link>
         <description><![CDATA[<div><strong><br>System Analysis</strong></div><div><strong><br>1.</strong>&nbsp; &nbsp; &nbsp; <strong>Analysis of current system achievement</strong></div><div><br>The systems analyst needs to know the details of current system functions: the who (the people who are involved), what (the business activity), where (the environment in which the work takes place), when (the timing), and how (how the current procedures are performed) of the business under study. The analyst must then ask why the business uses the current system. There may be good reasons for doing business using the current methods, and these should be considered when designing any new system.<br>&nbsp;<br><a href="http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/">http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/</a></div><div><strong><br>2.</strong>&nbsp; &nbsp; &nbsp; <strong>Analysis of a system’s user needs</strong></div><div><br>Understanding user requirements is an integral part of information systems design and is critical to the success of interactive systems. It is now widely understood that successful systems and products begin with an understanding of the needs and requirements of the users. As specified in the ISO 13407 standard (ISO, 1999), user-centred design begins with a thorough understanding of the needs and requirements of the users</div><div><br>The analyst will use various methods to pose and answer many questions concerning human-computer interaction (HCI), including questions such as, “What are the users’ physical strengths and limitations?” In other words, “What needs to be done to make the system audible, legible, and safe?” “How can the new system be designed to be easy to use, learn, and remember?” “How can the system be made pleasing or even fun to use?” “How can the system support a user’s individual work tasks and make them more productive in new ways?” In the information requirements phase of the SDLC, the analyst is striving to understand what information users need to perform their jobs. At this point the analyst is examining how to make the system useful to the people involved. How can the system better support individual tasks that need doing? What new tasks are enabled by the new system that users were unable to do without it? How can the new system be created to extend a user’s capabilities beyond what the old system provided? How can the analyst create a system that is rewarding for workers to use?<br>&nbsp;<a href="http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89.2102&amp;rep=rep1&amp;type=pdf">http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89.2102&amp;rep=rep1&amp;type=pdf</a></div><div><strong><br>3.</strong>&nbsp; &nbsp; &nbsp; <strong>Information gathering techniques</strong></div><div><br>The first step in user requirements analysis is to gather background information about the users and stakeholders and the processes that currently take place. The following methods may be adopted: Stakeholder analysis identifies all the users and stakeholders who may influence or be impacted by the system. This helps ensure that the needs of all those involved are taken into account. If required, the system is tested by them. User groups may include end users, supervisors, installers, and maintainers. Other stakeholders include recipients of output from the system, marketing staff, purchasers and support staff (Taylor, 1990). Stakeholder analysis identifies, for each user and stakeholder group, their main roles, responsibilities and task goals in relation to the system. One of the main issues is how to trade-off the competing needs of different stakeholder groups in the new system (see 4.5 Allocation of function and user cost-benefit analysis).</div><div><br>&nbsp;</div><div><br>Secondary market research involves researching published sources such as research reports, census data, demographic information, that throw light upon the range of possible user markets. Websites representing special groups of users such as that for the Royal National Institute for the Blind (www.rnib.org.uk/digital) give information about the nature of the user population they represent (Mander &amp; Smith, 2002).</div><div><br>&nbsp;</div><div><br>Task analysis involves the study of what a user is required to do in terms of actions and/or cognitive processes to achieve a task. A detailed task analysis can be conducted to understand the current system, the information flows within it, the problems for people, and opportunities that indicate user needs. There are many variations of task analysis and notations for recording task activities. One of the most widely used is hierarchical task analysis, where high level tasks are de-composed into more detailed components and sequences. Another method creates a flow chart showing the sequence of human activities and the associated inputs and outputs (Ericsson 2001). Kirwan &amp; Ainsworth (1992) provide a guide to the different task analysis methods, while Hackos &amp; Redish (1998) explain some of the simpler methods for user interface design.</div><div><strong><br>4.</strong>&nbsp; &nbsp; &nbsp; <strong>System’s analysis report</strong></div><div>A formal systems analysis report, prepared and presented to the steering committee, contains:</div><div>–reasons for system analysis</div><div>–scope of study</div><div>–problem identified with current system</div><div>–statement of user requirements</div><div>–resource implications</div><div>–recommendations</div><div><br>www.cengage.com/resource_uploads/downloads/1439078572_248443.pptx</div><div><strong><br>5.</strong>&nbsp; &nbsp; &nbsp; <strong>Accountant role in systems analysis&nbsp;</strong></div><div><br>The economic feasibility of proposed systems is of primary concern to accountants. Specifically, the accountant will ensure that:</div><div><br>• Only escapable costs are used in calculations of cost-savings benefits.</div><div><br>• Reasonable interest rates are used in measuring present values of cash flows.</div><div><br>• One-time and recurring costs are completely and accurately reported.</div><div><br>• Realistic useful lives are used in comparing competing projects.</div><div><br>• Intangible benefits are assigned reasonable financial values.</div><div><br>http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</div><div><strong><br><br>System Design&nbsp;</strong></div><div><strong><br>1.</strong>&nbsp; &nbsp; &nbsp; &nbsp;<strong>User interface design</strong></div><div><br>User Interface Design is the design of websites, computers, appliances, machines, mobile communication devices, and software applications with the focus on the user’s experience and interaction. The goal of user interface design is to make the user’s interaction as simple and efficient as possible, in terms of accomplishing user goals—what is often called user-centered design.</div><div><br>https://www.freshtilledsoil.com/what-is-user-interface-design/</div><div><strong><br>2.</strong>&nbsp; &nbsp; &nbsp; <strong>Output design</strong></div><div><br>Because useful output is essential to ensuring the use and acceptance of the information system, there are six objectives that the systems analyst tries to attain when designing output:</div><div><br>1.&nbsp; &nbsp; &nbsp; Designing output to serve the intended purpose.</div><div><br>2.&nbsp; &nbsp; &nbsp; Designing output to fit the user.</div><div><br>3.&nbsp; &nbsp; &nbsp; Delivering the appropriate quantity of output.</div><div><br>4.&nbsp; &nbsp; &nbsp; Making sure the output is where it is needed.</div><div><br>5.&nbsp; &nbsp; &nbsp; Providing the output on time.</div><div><br>6.&nbsp; &nbsp; &nbsp; Choosing the right output method.</div><div><br>http://www.w3computing.com/systemsanalysis/output-design-objectives/</div><div><strong><br>3.</strong>&nbsp; &nbsp; &nbsp; <strong>Input design</strong></div><div><br>Users deserve quality output. The quality of system input determines the quality of system output. It is vital that input forms, displays, and interactive Web documents be designed with this critical relationship in mind. Well-designed input forms, displays, and interactive Web fill-in forms should meet the objectives of effectiveness, accuracy, ease of use, consistency, simplicity, and attractiveness. All these objectives are attainable through the use of basic design principles, the knowledge of what is needed as input for the system, and an understanding of how users respond to different elements of forms and displays.<br><br></div><div><br>Effectiveness means that input forms, input displays, and fill-in forms on the Web all serve specific purposes for users of the information system, whereas accuracy refers to design that ensures proper completion. Ease of use means that forms and displays are straightforward and require no extra time for users to decipher. Consistency means that all input forms, whether they are input displays or fill-in forms on the Web, group data similarly from one application to the next, whereas simplicity refers to keeping those same designs uncluttered in a manner that focuses the user’s attention. Attractiveness implies that users will enjoy using input forms because of their appealing design.<br><br></div><div><br>http://www.w3computing.com/systemsanalysis/designing-effective-input-intro/<br><br></div><div><br>&nbsp;</div><div><strong><br>4.</strong>&nbsp; &nbsp; &nbsp; <strong>Security and control measures&nbsp;</strong></div><div><br>1.&nbsp; &nbsp; &nbsp; <strong>Audit and Accountability<br></strong><br></div><div><br>a)&nbsp; &nbsp; &nbsp; <strong>Enable process auditing or accounting</strong>: Enable process auditing or accounting, which generates logs information about the creation of new processes and their system activity.<br><br></div><div><br>b)&nbsp; &nbsp; &nbsp; <strong>Audit privilege escalation or change in privilege</strong>: Generate a log message whenever a user changes their level of privilege.<br><br></div><div><br>c)&nbsp; &nbsp; &nbsp; <strong>Audit firewall denial</strong>: Generate a log message when the host-based firewall denies a network connection.<br><br></div><div><br>d)&nbsp; &nbsp; &nbsp; <strong>Audit all significant application events</strong>: Log all significant application events.<br><br></div><div><br>e)&nbsp; &nbsp; &nbsp; <strong>Write audit events to a separate system</strong>: System logs must be written to a remote system in such a way that they cannot be altered by any user on the system being logged.<br><br></div><div><br>2.&nbsp; &nbsp; &nbsp; <strong>Configuration and Maintenance<br></strong><br></div><div><br>a)&nbsp; &nbsp; &nbsp; <strong>Follow advanced vendor security recommendations</strong>: This document cannot be comprehensive for all systems and applications available. Conform to best practices and recommendations outlined in vendor security whitepapers and documentation.<br><br></div><div><br>b)&nbsp; &nbsp; &nbsp; <strong>Host-based and network-based firewalls</strong>: Systems must be protected by both a host-based and a network-based firewall that allows only those incoming connections necessary to fulfill the business need of that system.<br><br></div><div><br>c)&nbsp; &nbsp; &nbsp; <strong>Configuration management process</strong>: Configuration changes must be regulated by a documented configuration and change management process.<br><br></div><div><br>d)&nbsp; &nbsp; &nbsp; <strong>Partitioning</strong>: Systems may share hardware and resources only with other systems that have similar security requirements, regardless of their <em>criticality</em> classification. Systems which share similar security requirements have user communities of similar size and character, similar firewall profiles, and similar technical requirements. For example:<br><br></div><div><br>1.&nbsp; &nbsp; &nbsp; Multiple systems of the same <em>criticality</em> may be aggregated together to share hardware and resources provided they have similar security requirements.<br><br></div><div><br>2.&nbsp; &nbsp; &nbsp; <em>High criticality</em> systems may share hardware and resources with <em>medium</em> and <em>low criticality</em> systems provided that all systems meet the <em>advanced systems Security Measures</em>, and share similar security requirements.<br><br></div><div><br>3.&nbsp; &nbsp; &nbsp; <strong>Additional Requirements<br></strong><br></div><div><br>a)&nbsp; &nbsp; &nbsp; <strong>Physical access</strong>: The system must reside in a secured, managed data-center. &nbsp;<br><br></div><div><br>https://www.nyu.edu/about/policies-guidelines-compliance/policies-and-guidelines/data-and-system-security-measures.html<br><br></div><div><br>&nbsp;</div><div><strong><br>5.</strong>&nbsp; &nbsp; &nbsp; <strong>Accountant role in systems designing</strong></div><div><br>Accountants are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument. This function of designing AIS includes the design of managerial accounting information system to aid management in decision making processes.</div><div><br>Many accountants relinquished their traditional responsibilities to the new generation of computer professionals who were emerging in their organizations. Computer programmers, often with no accounting or business training, assumed full responsibility for the design of accounting information systems. As a result, many systems violated accounting principles and lacked necessary controls. Large system failures and computer frauds marked this period in accounting history. By the mid-1970s, in response to these problems, the accounting profession began to reassess the accountant’s professional and legal responsibilities for computer-based systems.</div><div><br>The design of the conceptual system involves specifying the criteria for identifying delinquent customers and the information that needs to be reported. The accountant determines the nature of the information required, its sources, its destination, and the accounting rules that need to be applied. The physical system is the medium and method for capturing and presenting the information. The computer professionals determine the most economical and effective technology for accomplishing the task. Hence, systems design should be a collaborative effort. Because of the uniqueness of each system and the susceptibility of systems to serious error and even fraud, the accountant’s involvement in systems design should be pervasive.</div><div><br>http://bepls.com/beplsoctober2015/19.pdf</div><div><br>&nbsp;</div><div><br>&nbsp;</div><div><br>&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 03:01:18 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248355879</guid>
      </item>
      <item>
         <title>NOR SYUHADA BINTI ROCKY(BB15110485)</title>
         <author>syuhadarocky93</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248356423</link>
         <description><![CDATA[<div><strong><mark>System Analysis</mark></strong><strong><br></strong><br><strong>1.  Analysis of current system achievement</strong></div><div><br>The systems analyst needs to know the details of current system functions: the who (the people who are involved), what (the business activity), where (the environment in which the work takes place), when (the timing), and how (how the current procedures are performed) of the business under study. The analyst must then ask why the business uses the current system. There may be good reasons for doing business using the current methods, and these should be considered when designing any new system.<br><a href="http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/">http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/</a></div><div><br><strong>2. Analysis of a system's user needs<br>- </strong>Understanding user requirements is an integral part of information systems design and is critical to the success of interactive systems.<br>- It is now widely understood that successful systems and products begin with an understanding of the needs and requirements of the users. <br>- As specified in the ISO 13407 standard (ISO, 1999), user-centred design begins with a thorough understanding of the needs and requirements of the users. <br>-The benefits can include increased productivity, enhanced quality of work, reductions in support and training costs, and improved user satisfaction. <br><br><a href="http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89.2102&amp;rep=rep1&amp;type=pdf">http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89.2102&amp;rep=rep1&amp;type=pdf</a><br><strong>3.information gathering techniques<br>- </strong>Information gathering includes various techniques like brainstorming, Delphi technique, interviews and root cause analysis. The ultimate aim of all these techniques is to identify and prepare a comprehensive list of risks in the project.<br>- there are 4 types of information gathering techniques:<br><br>1<mark>)</mark><strong><mark>Brainstorming</mark></strong></div><div>- It is one of the most widely used techniques to identify risks in a project. Project team usually performs brainstorming, often with subject matter experts, risk management experts and other important stakeholders who can contribute to the risk identification. It allows people to come up with risks.<br>- During brainstorming sessions there should be no criticism of ideas.<br><mark>2)</mark><strong><mark>Delphi technique</mark></strong></div><div>- This technique is used to build consensus of experts who participate anonymously. A facilitator uses a questionnaire to solicit ideas about important project risks. The questionnaire is often designed with forced choices that require the experts to select between various options. <br>- Delphi technique helps reduce bias in the data and keeps any one person from having undue influence on the outcome.<br><mark>3)</mark><strong><mark>Interviewing</mark></strong></div><div>- Interviewing is generally a face-to-face meeting that includes question and answer sessions. The interviews are conducted with project manager, project team, stakeholders, subject-matter experts, and individuals who may have participated in similar, past projects.<br>- Interviews help us to get first-hand information about others' experience and knowledge.</div><div><mark>4) </mark><strong><mark>Root cause analysis</mark></strong></div><div>- Root cause identification is a technique for identifying essential causes of risk. Reorganizing the identified risks by their root causes will help to identify more risks. <br>-This technique enables you to understand the risk more clearly so that responses can be planned to prevent recurrences.<br><a href="http://www.justgetpmp.com/2012/02/information-gathering-techniques.html">http://www.justgetpmp.com/2012/02/information-gathering-techniques.html</a></div><div><strong><br></strong><br><strong>4. System's analysis report</strong><br>- The purpose of this report is to present the proposed system analysis for the client, Click &amp; Connect, with the intention of ensuring all stakeholders involved agree on the planned solution. Throughout the project the analysis, development, implementation and testing phases will be conducted using, the industry standard, agile development life cycle. This specifies that changes can be made if required and appropriate. The system analysis report is intended for all the project's major stakeholders: the client, the academic supervisors and the development team.<br><a href="https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php">https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php</a></div><div><br><br><strong>5. Accountant role in systems analysis</strong><br><br></div><div>- Accountants may perform certain types of analysis using financial data that is used to assist in making business decisions. From deciding which kinds of supplies to order, payment of bills to payroll, the accountant handles many intricate financial details on a daily basis. <br>- Advising on business operations can include issues, such as revenue and expenditure trends, financial commitments and future revenue expectations. <br>-The accountant also analyzes financial data to resolve certain discrepancies and irregularities that may arise. <br>-Recommendations may also involve developing efficient resources and procedures, while providing strategic recommendations for specific financial problems or situations<br><br><br><br></div><div><br><strong><mark>System Design</mark></strong></div><div><strong>1. User interface design</strong><br>User interface design  or UI design generally refers to the visual layout of the elements that a user might interact with in a website, or technological product. This could be the control buttons of a radio, or the visual layout of a webpage. User interface designs must not only be attractive to potential users, but must also be functional and created with users in mind.<br><a href="https://pidoco.com/en/help/ux/user-interface-design">https://pidoco.com/en/help/ux/user-interface-design</a><br><br><strong>2. Output design</strong></div><div>-  The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.<br><br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br><strong>3. Input design</strong></div><div>- In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.<br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br><strong>4. Security and control measure.</strong><br><br></div><div>The Security and Control Measures category encompasses the core activities directly related to protection and accounting of nuclear materials. It includes indicators of physical protection, control and accounting, insider threat prevention, security during transport, response capabilities, and a new cybersecurity indicator.</div><div><a href="http://ntiindex.org/indicators/security-and-control-measures/">http://ntiindex.org/indicators/security-and-control-measures/</a><br><br>5. Accountant role in systems designing<br> </div><div>- Accountants are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument. This function of designing AIS includes the design of managerial accounting information system to aid management in decision making processes. An appreciation of the accountant<br>-As responsibility for system design requires a historic perspective that predates the computer as a business information tool. <br>- Traditionally, accountants have been responsible for key aspects of the information system, including assessing the information needs of users, defining the content and format of output reports, specifying sources of data, selecting the appropriate accounting rules, and determining the controls necessary to preserve the integrity and efficiency of the information system. <br><br><br></div><div><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 03:06:38 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248356423</guid>
      </item>
      <item>
         <title>NOR ASLINDA BINTI RUSLAN</title>
         <author>aslindaruslan96</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248364092</link>
         <description><![CDATA[<div>BB15110474<br><strong>System Analysis<br></strong>It is a process of collecting and interpreting facts, identifying the problems, and decomposition of a system into its components.<br>System analysis is conducted for the purpose of studying a system or its parts in order to identify its objectives. It is a problem solving technique that improves the system and ensures that all the components of the system work efficiently to accomplish their purpose.Analysis specifies what the system should do.<br><strong>1. Analysis of current system achievement<br></strong>Current systems analysis technique is used to evaluate the degree of support provided by current systems to the business activities of the enterprise. Assessments of user and technical satisfaction are performed and data, procedures and problems are analyzed. <br><strong>Purpose</strong><br>The purpose of current systems analysis technique is to identify shortcomings and issues with current systems. It is used to assess the usefulness, usability, and overall user satisfaction with the current systems to facilitate decision making concerning the current systems’ strategic and tactical viability.<br><strong>Benefits</strong><br>The current systems analysis technique provides a comprehensive and objective method for assessing current systems.<br><a href="https://www.projectmanagement.com/process/popup.cfm?ID=23401">https://www.projectmanagement.com/process/popup.cfm?ID=23401</a><strong><br>2. Analysis of a system's user needs<br>T</strong>he developer must know the user and understanding their needs.</div><ul><li>Poorly specified user requirements are one of the most significant factors behind IT project failure.</li><li>A successful product or system requires a proper understanding of both user and organisational requirements - we help integrate and balance the two in the specification process.</li><li>Avoid over-reliance on internally generated requirements (what its believed that users want), as opposed to data from end-user requirements studies (what users actually need).</li><li>Usability Partners support development projects, bringing key user data into the design process and analysing user needs, their work practice, and the situations in which they work.&nbsp;</li></ul><div><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a></div><div><strong>3.information gathering techniques<br></strong><em>There are many different methods used by systems analysts to gather the information required to design an information system. It is vital that they gather relevant information from the client that clearly outlines what they want the system to do and what it should be capable of doing. Otherwise&nbsp; the system created will just be a waste of the analysts time and resources. And so I am going to go in to a bit more detail about the traditional methods they use to gather information since it is so crucial in their job </em><br><strong>Traditional methods<br>1. Interviews</strong><br><em>The aim of an interview is to gather information, facts and opinions from the person being interviewed through a series of insightful questions. It is important that the systems analyst plans the questions they plan to ask in advance in order to ensure they gather all the necessary information and detail they require. An interview allows the interviewee to provide long, detailed answers if they require and it provides the interviewer the opportunity to respond and ask questions that may stem from the answers given. <br></em>&nbsp;<strong>2.&nbsp; Questionnaires<br></strong>Questionnaires are another traditional method used by systems analysts. There are often more questions in a questionnaire than in an interview so it is another important source of information for the analyst before they begin designing the information system. Questions featured on a survey can be open or closed. A questionnaire allows the subject time to think about their answer and time to recall previous events or thoughts. Another advantage of questionnaires is that they are less time consuming than interviews.</div><div><strong><em>3. Observation<br></em></strong><em>This method involves the system analyst observing their client in their daily routine in order to gather information. It is a good method to use along with interviews however it is a flawed method; some people may act differently when they know they are being observed. <br></em><a href="https://eternalsunshineoftheismind.wordpress.com/2013/03/05/methods-used-by-systems-analysts-to-gather-information/"><em>https://eternalsunshineoftheismind.wordpress.com/2013/03/05/methods-used-by-systems-analysts-to-gather-information/</em></a><em><br>Other techniques are<br>4)</em><strong>Facilitated sessions<br></strong>In a facilitated session, you bring a larger group (five or more) together for a common purpose. In this case, you are trying to gather a set of common requirements from the group in a faster manner than if you were to interview each of them separately.<br>5)<strong>Joint application development (JAD)<br></strong>JAD sessions are similar to general facilitated sessions. However, the group typically stays in the session until the session objectives are completed. For a requirements JAD session, the participants stay in session until a complete set of requirements is documented and agreed to.<br>6)<strong>Prototyping<br></strong>Prototyping is a relatively modern technique for gathering requirements. In this approach, you gather preliminary requirements that you use to build an initial version of the solution — a prototype. You show this to the client, who then gives you additional requirements. You change the application and cycle around with the client again. This repetitive process continues until the product meets the critical mass of business needs or for an agreed number of iterations.<br>7)<strong>Use cases<br></strong>Use cases are basically stories that describe how discrete processes work. The stories include people (actors) and describe how the solution works from a user perspective. Use cases may be easier for the users to articulate, although the use cases may need to be distilled later into the more specific detailed requirements.<br>8)<strong>Following people around<br></strong>This technique is especially helpful when gathering information on current processes. You may find, for instance, that some people have their work routine down to such a habit that they have a hard time explaining what they do or why. You may need to watch them perform their job before you can understand the entire picture. In some cases, you might also want to participate in the actual work process to get a hands-on feel for how the business function works today.<br>9)<strong>Request for proposals (RFPs)<br></strong>If you are a vendor, you may receive requirements through an RFP. This list of requirements is there for you to compare against your own capabilities to determine how close a match you are to the client's needs.<br>10)<strong>Brainstorming<br></strong>On some projects, the requirements are not "uncovered" as much as they are "discovered." In other words, the solution is brand new and needs to be created as a set of ideas that people can agree to. In this type of project, simple brainstorming may be the starting point. The appropriate subject matter experts get into a room and start creatively brainstorming what the solution might look like. After all the ideas are generated, the participants prioritize the ones they think are the best for this solution. The resulting consensus of best ideas is used for the initial requirements.<br><a href="https://www.techrepublic.com/blog/10-things/10-techniques-for-gathering-requirements/">https://www.techrepublic.com/blog/10-things/10-techniques-for-gathering-requirements/</a><br><strong>4. System's analysis report<br></strong>System analysis report provides the detailed analyses that support a System Evaluation Report (SER). It accounts for all issues and measures contained in the System Evaluation Plan. A SAR is also prepared to support a System Assessment (SA) when the analysis is too detailed or inappropriate for inclusion in the SA and addresses only those issues and measures contained in the SA.<br><a href="https://definedterm.com/system_analysis_report">https://definedterm.com/system_analysis_report</a><strong><br>5. Accountant role in systems analysis</strong></div><div><strong>THE ACCOUNTANT’S ROLE IN SYSTEMS SELECTION</strong>&nbsp;<br>The economic feasibility of proposed systems is of primary concern to accountants. Specifically, the accountant should ensure that:&nbsp;<br>&nbsp;</div><blockquote>• Only escapable costs are used in calculations of cost-savings benefits.<br><br>• Reasonable interest rates are used in measuring present values of cash flows.<br><br>• One-time and recurring costs are completely and accurately reported.<br><br>• Realistic useful lives are used in comparing competing projects.<br><br>• Intangible benefits are assigned reasonable financial values.<br><br></blockquote><div>Errors, omissions, and misrepresentations in the accounting for such items can distort the analysis and result in a suboptimal decision. <br><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a></div><div><strong>System Design<br></strong>It is a process of planning a new business system or replacing an existing system by defining its components or modules to satisfy the specific requirements. Before planning, you need to understand the old system thoroughly and determine how computers can best be used in order to operate efficiently.<br>System Design focuses on how to accomplish the objective of the system.<br><strong>1 User interface design<br></strong>User interface (UI) design is the design of user interfaces for software or machines, such as the look of a mobile app, with a focus on <em>ease of use</em> and <em>pleasurability</em> for the user. UI design usually refers to the design of graphical user interfaces—but can also refer to others, such as natural and voice user interfaces.<br><br></div><div>Since software is intangible, the only way a user can control or interact with it is through a designed user interface. A well-designed user interface creates a user experience that the designer intended and/or a user experience that the user appreciates.<br><br></div><div>Many user interfaces are designed with a focus on <em>usability</em> and <em>efficiency</em>. Users should be able to achieve their goals as efficiently as possible, without focusing too much on the user interface itself. In that sense, a well-designed user interface becomes effectively <em>invisible</em> to those using it. In other words, they interact directly with the ‘reality’ the design portrays without reckoning on the point that, for example, thumbing button icons through the glass screens of their handheld devices is responsible for producing changes in what they see. However, usability and efficiency might not be the only measure of a well-designed user interface; a user interface might be designed to create a fun and pleasurable experience for users instead (e.g., in games).<br><br></div><div>At the other end of the spectrum, designers can—unethically—deliberately design user interfaces that are confusing—in order to trick users into purchasing or signing up for things they might not be interested in. These user interfaces are known as <em>dark patterns</em>. Examples of dark patterns include add-ons that are included by default (e.g., additional luggage allowance when booking air tickets), and intentionally complicated processes meant to deter users (e.g., long and confusing pages to unsubscribe from email newsletters).<br><strong>2. Output design</strong></div><div>The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.</div><div><strong>Objectives of Output Design</strong><br><br></div><div>The objectives of input design are&nbsp;</div><ul><li>To develop output design that serves the intended purpose and eliminates the production of unwanted output.<br><br></li><li>To develop the output design that meets the end users requirements.<br><br></li><li>To deliver the appropriate quantity of output.<br><br></li><li>To form the output in appropriate format and direct it to the right person.<br><br></li><li>To make the output available on time for making good decisions.&nbsp;</li></ul><div>&nbsp;</div><div>T<strong>ypes of outputs</strong><br><strong>External Outputs</strong><br>Manufacturers create and design external outputs for printers. External outputs enable the system to leave the trigger actions on the part of their recipients or confirm actions to their recipients.<br><br></div><div>Some of the external outputs are designed as turnaround outputs, which are implemented as a form and re-enter the system as an input.</div><div><strong>Internal outputs</strong><br><br></div><div>Internal outputs are present inside the system, and used by end-users and managers. They support the management in decision making and reporting.<br><br></div><div>There are three types of reports produced by management information −<br><br></div><ul><li><strong>Detailed Reports</strong> − They contain present information which has almost no filtering or restriction generated to assist management planning and control.<br><br></li><li><strong>Summary Reports</strong> − They contain trends and potential problems which are categorized and summarized that are generated for managers who do not want details.<br><br></li><li><strong>Exception Reports</strong> − They contain exceptions, filtered data to some condition or standard before presenting it to the manager, as information.</li></ul><div><strong>Output Integrity Controls</strong></div><div>Output integrity controls include routing codes to identify the receiving system, and verification messages to confirm successful receipt of messages that are handled by network protocol.<br><br></div><div>Printed or screen-format reports should include a date/time for report printing and the data. Multipage reports contain report title or description, and pagination. Pre-printed forms usually include a version number and effective date. <br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a></div><div><br><strong>3. Input design<br></strong>The input design is the link between the information system and the user. It comprise the developing specification and procedures for data preparation and those steps are necessary to put transaction data in to a unable from for processing can be achieved by inspecting the computer to read data from a written or printed document or it can occur by having people keying the data directly into the system.<strong><br></strong>System design takes the following inputs :<br>-Statement of work<br>-Requirement determination plan<br>-Current situation analysis<br>-Proposed system requirements including a conceptual data model, modified DFDs, and Metadata (data about data).<br><a href="https://www.slideshare.net/madhukarreddy007/input-and-output-design">https://www.slideshare.net/madhukarreddy007/input-and-output-design</a><br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_design.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_design.htm</a></div><div><strong>4. Security and control measures<br>-Security</strong><br>System security refers to protecting the system from theft, unauthorized access and modifications, and accidental or unintentional damage. In computerized systems, security involves protecting all the parts of computer system which includes data, software, and hardware. Systems security includes system privacy and system integrity.</div><ul><li><strong>System privacy</strong> deals with protecting individuals systems from being accessed and used without the permission/knowledge of the concerned individuals.</li><li><strong>System integrity</strong> is concerned with the quality and reliability of raw as well as processed data in the system.</li></ul><div><strong>Control Measures</strong><br>There are variety of control measures which can be broadly classified as follows −<br><strong>Backup</strong></div><ul><li>Regular backup of databases daily/weekly depending on the time criticality and size.</li><li>Incremental back up at shorter intervals.</li><li>Backup copies kept in safe remote location particularly necessary for disaster recovery.</li><li>Duplicate systems run and all transactions mirrored if it is a very critical system and cannot tolerate any disruption before storing in disk.</li></ul><div><strong>Physical Access Control to Facilities</strong></div><ul><li>Physical locks and Biometric authentication. For example, finger print</li><li>ID cards or entry passes being checked by security staff.</li><li>Identification of all persons who read or modify data and logging it in a file.</li></ul><div><strong>Using Logical or Software Control</strong></div><ul><li>Password system.</li><li>Encrypting sensitive data/programs.</li><li>Training employees on data care/handling and security.</li><li>Antivirus software and Firewall protection while connected to internet.</li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm</a></div><div><strong>5. Accountant role in systems designing<br></strong>The stage of design aims to implement the following activities ( Al-Hasun and Al-Qaisi, 1999, Al-Ghitani, 2000, Atiyah, 2000, Bashadi, et al. 2005, Debian, et al. 2005, Hussein, 2006): - Designing the procedures and processes required for meeting the requirements of the system; - <br>--Identifying accurately the requirements of the programs and organizing the files and databases; - Designing the documents of inputs and outputs required for the system <br>- Designing the manual of accounts<br>- Designing the manual of procedures<br>&nbsp;- Designing the screens which will be displayed to the users<br>- Designing the appropriate types and formats of the reports as well as identifying their contents<br>- Identifying the method and the time of submitting the reports<br>- Establishing various relations between the programs and the data<br>- Establishing the procedures of the internal control of the system<br>- Identifying the methods of entering and getting out the financial data<br><a href="https://ijbssnet.com/journals/Vol_5_No_4_Special_Issue_March_2014/31.pdf">https://ijbssnet.com/journals/Vol_5_No_4_Special_Issue_March_2014/31.pdf</a></div><div><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 04:20:58 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248364092</guid>
      </item>
      <item>
         <title>AMALINA BINTI NORAZAM</title>
         <author>amalinanorazam04</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248364203</link>
         <description><![CDATA[<div><strong>(BB15110086)<br><br>System Analysis<br></strong><mark>1)Analysis of current system achievement<br></mark>Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. A key question is, what must be done to solve the problem? One aspect of analysis is defining the boundaries of the system and<br>determining whether or not a candidate system should consider other related systems. During analysis, data are collected on the available files, decision points, and transactions handled by the present system. Data flow diagrams interviews, on – site observations, and questionnaires are examples of the analysis tools. The interviews is a commonly used tool in analysis, it requires special skills and sensitivity to the subjects being interviewed. Bias<br>in data collection and interpretation can be a problem. Training, experience, and common<br>sense are required for collection of the information needed to do the analysis.<br><br></div><div><mark>2)Analysis of a system’s user needs<br></mark>Users and analysts traditionally do not share a common orientation toward problem definition. For example, in the analyst’s view the problem definition must be translatable into a system design expressed quantitatively in terms of outputs, inputs, processes and data structures. This is the best of situations, and within time constraints. In contrast, the user seems to be satisfied with a qualitative definition that specifies the system in generalities. Flexibility is a key consideration. System specifications must change with their needs, as must the system after implementation. <mark><br></mark><br><mark>3)Information gathering techniques<br></mark><em>-One-on-one interviews</em><br>The most common technique for gathering requirements is to sit down with the clients and ask them what they need. The discussion should be planned out ahead of time based on the type of requirements you're looking for.<br><em>-Group interviews</em><br>Group interviews are similar to the one-on-one interview, except that more than one person is being interviewed — usually two to four. These interviews work well when everyone is at the same level or has the same role. Group interviews require more preparation and more formality to get the information you want from all the participants.<br><em>-Questionnaires</em><br>Questionnaires are much more informal, and they are good tools to gather requirements from stakeholders in remote locations or those who will have only minor input into the overall requirements. Questionnaires can also be used when you have to gather input from dozens, hundreds, or thousands of people.<br><em>-Prototyping</em><br>Prototyping is a relatively modern technique for gathering requirements. In this approach, you gather preliminary requirements that you use to build an initial version of the solution — a prototype. You show this to the client, who then gives you additional requirements. You change the application and cycle around with the client again. <br><em>-Brainstorming</em><br>On some projects, the requirements are not "uncovered" as much as they are "discovered." In other words, the solution is brand new and needs to be created as a set of ideas that people can agree to. In this type of project, simple brainstorming may be the starting point. The appropriate subject matter experts get into a room and start creatively brainstorming what the solution might look like. <br><a href="https://www.techrepublic.com/blog/10-things/10-techniques-for-gathering-requirements/">https://www.techrepublic.com/blog/10-things/10-techniques-for-gathering-requirements/</a><br><br><mark>4)System’s analysis report<br></mark><strong>(as attached on image below)</strong><mark><br></mark><br><mark>5)Accountant role in systems analysis</mark><br>-Accountants are involved in systems development in three ways. First, accountants are users. All systems that process financial transactions impact the accounting function in some way. Like all users, accountants must provide a clear picture of their problems and needs to the systems professional. For example, accountants must specify accounting techniques to be used; internal control requirements, such as audit trails; and special algorithms, such as depreciation models.<br>-Second, accountants participate in systems development as members of the development team. Their involvement often extends beyond the development of strictly accounting information systems applications. Systems that do not process financial transactions may still draw on accounting data. The accountant may be consulted to provide advice or to determine if the proposed system constitutes an internal control risk.<br>-Third, accountants are involved in systems development as auditors. Accounting information systems must be audit-able. Some computer audit techniques require special features that must be designed into the system. The auditor/accountant has a stake in such systems and must be involved early in their design.<br><br><strong>System Design</strong><br><mark>1)User interface design<br></mark><em>-Keep the interface simple</em>. <br>-<em>Create consistency and use common user interface (UI) elements.</em><br><em>-Be purposeful in page layout.<br>- Strategically use colour and texture. <br>-Use typography to create hierarchy and clarity.<br>-Make sure that the system communicates what’s happening. <br>-Think about the defaults.<br></em><br><mark>2)Output design<br></mark>consists of general design, detail design, program specs.<br><br><mark>3)Input design</mark><br>consists of environments, system components.<br><br><mark>4)Security and control measures</mark> <br>Security has to be considered at all stages of the life cycle of an information system (i.e., feasibility, planning, development, implementation, maintenance, and retirement) in order to:<br>-ensure conformance with all appropriate security requirements,<br>-protect sensitive information throughout its life cycle,<br>-facilitate efficient implementation of security controls,<br>-prevent the introduction of new risks when the system is modified, and<br>-ensure proper removal of data when the system is retired. This policy provides guidance to ensure that systems security is considered during the Acquisition, Development and Maintenance and Testing Stages of an information system's life cycle.<br><br><mark>5)Accountant role in systems designing </mark><br>Accountants are involved in the SDLC since information systems represent a significant financial transaction that consumes both financial and human resources. The accountants are concerned with these projects since they have significant financial resource implications. Also, accountants are concerned with the quality of the accounting information systems since these systems produce the information that is reported to internal and external entities. Accountants may be called upon for input into non-AIS applications if the application uses accounting data. The accountants need to assess if any control threats exist.</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/221474457/1933b1caa7bba7442b4e910bf0b93ccf/ch006_f004.jpg" />
         <pubDate>2018-04-04 04:22:23 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248364203</guid>
      </item>
      <item>
         <title>NURUL HIDAYAH BINTI KHAIRONI(BB15110589)</title>
         <author>hidayahkhaironi</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248365952</link>
         <description><![CDATA[<div><strong>Lecture 5: System Analysis &amp; Design<br></strong><em>Systems Analysis and Design is an active field in which analysts repetitively learn new approaches and different techniques for building the system more effectively and efficiently. The primary objective of systems analysis and design is to improve organizational systems. </em><em><mark><br></mark></em><em>(</em><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf"><em>https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf</em></a>)<br><br><br>[<strong>System Analysis]<br></strong><em>It is a process of collecting and interpreting facts, identifying the problems, and decomposition of a system into its components. System analysis is conducted for the purpose of studying a system or its parts in order to identify its objectives. It is a problem solving technique that improves the system and ensures that all the components of the system work efficiently to accomplish their purpose. Analysis specifies what the system should do. <br>(</em><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf"><em>https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf</em></a><em>)</em><strong><br></strong><br></div><div>&nbsp; <strong><mark>1. Analysis of current system achievement</mark></strong></div><div><em>The systems analyst needs to know the details of current system functions: the who (the people who are involved), what (the business activity), where (the environment in which the work takes place), when (the timing), and how (how the current procedures are performed) of the business under study. The analyst must then ask why the business uses the current system. There may be good reasons for doing business using the current methods, and these should be considered when designing any new system.</em></div><div><br></div><div>&nbsp; <strong><mark>2. Analysis of a system’s user needs<br></mark></strong><em>Typical requirements gathering and analysis methods include:</em></div><ul><li><em>Surveys – both open-ended and focused surveys, conducted electronically or on paper.</em></li><li><em>Interviews – typically conducted face-to-face, but also over the telephone if deemed more appropriate.</em></li><li><em>Focus groups – whilst being poorly suited to evaluating a product, focus groups are useful for discussing possible user requirements and brainstorming ideas.</em></li><li><em>Field studies – observing the end-user situation and the environment in which a new product or system will be used is often extremely useful in understanding user needs.</em></li><li><em>Evaluation of an existing product – provides a range of useful information (even competitor products can be tested). Usability evaluation reveals and clarifies good and bad aspects of current solutions - valuable input to new design work.</em></li><li><em>Task analysis – a deeper analysis of users work with a system, useful for analysing how user's work tasks should be supported by functionality in a system.</em></li><li><em>User personas and usage scenarios – concrete and illustrative data about typical users, their characteristics, usage situation, tasks and goals. Particularly useful in supporting early user interface design work.</em></li><li><em>Formulation of usability goals and overall design criteria – help focus and steer the design process, supporting the evaluation of early concepts, prototypes and final designs.</em></li></ul><div><br>(<a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a>)</div><div><br></div><div>&nbsp;<mark>&nbsp;</mark><strong><mark>3. Information gathering techniques</mark></strong><strong><br></strong><em>The main aim of fact finding techniques is to determine the information requirements of an organization used by analysts to prepare a precise SRS understood by user. Ideal SRS Document should: <br> be complete, Unambiguous, and Jargon-free. <br> specify operational, tactical, and strategic information requirements.  solve possible disputes between users and analyst.<br> use graphical aids which simplify understanding and design. There are various information gathering techniques: <br>1)Interviewing<br>2)Questionnaires<br>3)Reviews of record, procedures and forms<br>4)Observation<br>5)Joint Application Development(JAD)<br>6)Secondary research or background reading</em><strong><br></strong><em>(</em><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf"><em>https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf</em></a><em>)<br></em><br></div><div><strong><mark>4. System’s analysis report<br></mark></strong>&nbsp;<em>The purpose of this report is to present the proposed system analysis for the client with the intention of ensuring all stakeholders involved agree on the planned solution. Throughout the project the analysis, development, implementation and testing phases will be conducted using, the industry standard, agile development life cycle. This specifies that changes can be made if required and appropriate. The system analysis report is intended for all the project's major stakeholders: the client, the academic supervisors and the development team.<br>(</em><a href="https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php"><em>https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php</em></a><em>)</em><strong><br></strong><br></div><div><strong><mark>5.Accountant role in systems analysis </mark></strong><strong><br></strong>&nbsp;<em>Accountants are involved in systems development in three ways. <br>&nbsp; &nbsp; First, accountants are users. All systems that process financial transactions impact the accounting function in some way. Like all users, accountants must provide a clear picture of their problems and needs to the systems professional. For example, accountants must specify accounting techniques to be used; internal control requirements, such as audit trails; and special algorithms, such as depreciation models.<br>&nbsp; &nbsp; Second, accountants participate in systems development as members of the development team. Their involvement often extends beyond the development of strictly accounting information systems applications. Systems that do not process financial transactions may still draw on accounting data. The accountant may be consulted to provide advice or to determine if the proposed system constitutes an internal control risk.<br>&nbsp; &nbsp; Third, accountants are involved in systems development as auditors. Accounting information systems must be auditable. Some computer audit techniques require special features that must be designed into the system. The auditor/accountant has a stake in such systems and must be involved early in their design. <br><br>(</em><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/"><em>http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</em></a><em>)</em></div><div><strong><br>[System Design]<br></strong><em>It is a process of planning a new business system or replacing an existing system by defining its components or modules to satisfy the specific requirements. Before planning, you need to understand the old system thoroughly and determine how computers can best be used in order to operate efficiently. System Design focuses on how to accomplish the objective of the system.<br>(</em><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf"><em>https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf</em></a><em>)</em><strong><br><br></strong><strong><mark>1. User interface design</mark></strong><strong><br></strong><em>&nbsp;User Interface Design is the design of websites, computers, appliances, machines, mobile communication devices, and software applications with the focus on the user’s experience and interaction. The goal of user interface design is to make the user’s interaction as simple and efficient as possible, in terms of accomplishing user goals—what is often called user-centered design.</em></div><div><em><br>(</em><a href="https://www.freshtilledsoil.com/what-is-user-interface-design/"><em>https://www.freshtilledsoil.com/what-is-user-interface-design/</em></a><em> )</em></div><div><strong><br></strong><br></div><div><strong><mark>2.</mark></strong><mark> </mark><strong><mark>Output design</mark></strong><strong><br></strong><em>The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts. Objectives of Output Design The objectives of ouput design are: <br> To develop output design that serves the intended purpose and eliminates the production of unwanted output. <br> To develop the output design that meets the end users requirements.  To deliver the appropriate quantity of output. <br> To form the output in appropriate format and direct it to the right person. <br> To make the output available on time for making good decisions. <br><br>(</em><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf"><em>https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf</em></a><em>)</em><strong><em><br></em></strong><strong><br></strong><br></div><div><strong><mark>3. Input design</mark></strong><strong><br></strong><em>In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc. Therefore, the quality of system input determines the quality of system output. Well designed input forms and screens have following properties: <br> It should serve specific purpose effectively such as storing, recording, and retrieving the information.<br> It ensures proper completion with accuracy.<br> It should be easy to fill and straightforward.<br> It should focus on user’s attention, consistency, and simplicity.<br> All these objectives are obtained using the knowledge of basic design principles regarding on what are the inputs needed for the system and on how end users respond to different elements of forms and screens. <br><br>(</em><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf"><em>https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf</em></a><em>)</em><strong><em><br></em></strong><br></div><div><strong><mark>4. Security and control measures <br></mark></strong><em>System security refers to protecting the system from theft, unauthorized access and modifications, and accidental or unintentional damage. In computerized systems, security involves protecting all the parts of computer system which includes data, software, and hardware. Systems security includes system privacy and system integrity.</em></div><ul><li><em>System privacy deals with protecting individuals systems from being accessed and used without the permission/knowledge of the concerned individuals.</em></li><li><em>System integrity is concerned with the quality and reliability of raw as well as processed data in the system.</em></li></ul><div><br></div><div><em>(</em><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm"><em>https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm</em></a><em>)</em></div><div><strong><br></strong><br></div><div><strong><mark>5. Accountant role in systems designing</mark></strong><strong><br></strong><em>The accountant plays an important role in the conceptual design of the system. He or she must recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood. These issues need not be specified in detail at this point, but they should be recognized as items to be addressed during the construct phase of the system. Furthermore, the auditability of a system depends in part on its design characteristics. Some computer auditing techniques require systems to be designed with built-in audit features. Such features require resources and need to be considered at conceptual design.<br><br>(</em><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/"><em>http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</em></a><em>)<br></em><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 04:39:41 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248365952</guid>
      </item>
      <item>
         <title>JEEVANRAJ A/L RAJA BB15110270</title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248366639</link>
         <description><![CDATA[<div>1. Analysis of current system achievement&nbsp;<br>2. Analysis of system user needs<br>3.information gathering techniques<br>4 Accounting role in system analysis<br>5. system analysis report<br>&nbsp;<br>System Design<br>&nbsp;1. output design<br>2.user interface design<br>3.security and control measure<br>4. Accounting role in system designing<br>5.input design</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 04:47:50 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248366639</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248368289</link>
         <description><![CDATA[]]></description>
         <enclosure url="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm" />
         <pubDate>2018-04-04 05:05:39 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248368289</guid>
      </item>
      <item>
         <title>CHORLELINA LABI (BB15110153)</title>
         <author>Chorlelina</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248368315</link>
         <description><![CDATA[<div><strong>System Analysis<br><br>1. Systems analysis</strong> is a problem-solving method that involves looking at the wider system, breaking apart the parts, and figuring out how it works in order to achieve a particular goal. System analysis will improved performance and a feeling of achievement with quality information </div><div><a href="https://study.com/academy/lesson/systems-analysis-definition-example.html">https://study.com/academy/lesson/systems-analysis-definition-example.html</a><br><br><a href="http://www.ddegjust.ac.in/studymaterial/mca-3/ms-04.pdf">http://www.ddegjust.ac.in/studymaterial/mca-3/ms-04.pdf</a></div><div><br>2. Analysis of a system’s user needs<br>First, the system must be high specified user requirement. Second need a proper understanding of both user and organizational requirement. Third, avoid over-reliance on what its believed that users want with what user actually need.<br><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a><br><br>3.Information gathering techniques<br> </div><div>There's few technique to gather information that is :</div><ul><li><em>Surveys</em> –  conducted electronically or on paper.</li><li><em>Interviews</em> – conducted face-to-face.</li><li> <em>Evaluation of an existing product</em> – provides a range of useful information (even competitor products can be tested) </li><li><em>Task analysis</em> – a deeper analysis of users work with a system, useful for analysing how user's work tasks should be supported by functionality in a system. </li></ul><div><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a><br><br>4. System’s analysis report<br>System analysis report provides the detailed analyses that support a System Evaluation Report (SER). It accounts for all issues and measures contained in the System Evaluation Plan. <br><a href="https://definedterm.com/system_analysis_report">https://definedterm.com/system_analysis_report</a><br><br>5.Accountant role in systems analysis </div><div>First is as an a user.  accountants must provide a clear picture of their problems and needs to the systems professional. <br>Second as an auditor.  Accountant will help to require special features that must be designed into the system. <br><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a><br><strong><br>System Design <br><br>1. </strong>User interface design<br>User Interface design is is the design of user interfaces for software, such as computers with the focus on maximizing usability and the user experience.  Design focuses on anticipating what users might need to do and ensuring that the interface has elements that are easy to access, understand, and use to facilitate those actions. <br><a href="https://en.wikipedia.org/wiki/User_interface_design">https://en.wikipedia.org/wiki/User_interface_design</a><br><br><a href="https://www.usability.gov/what-and-why/user-interface-design.html">https://www.usability.gov/what-and-why/user-interface-design.html</a><br><br>2. Output design<br>In output design the developers will identify the type of outputs needed, and consider the necessary output controls and prototype report layouts. Output design will develop the output design that meets the end users requirements. <br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br>3. Input design<br>Input design is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC.<br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br>4. Security and control measures<br>Security and control refer to measures or techniques that prevent , detect, and/or correct conditions that may lead to</div><div>loss or damage to the business firm.<br><a href="https://www.scribd.com/document/173360890/Systems-Controls-and-Security-Measures-in-an-Accounting-Information-System-Paprint">https://www.scribd.com/document/173360890/Systems-Controls-and-Security-Measures-in-an-Accounting-Information-System-Paprint</a></div><div><br>5.Accountant role in systems designing</div><div>Accountant will recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood.<br><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 05:05:54 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248368315</guid>
      </item>
      <item>
         <title></title>
         <author>jackhazlyne1</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248369131</link>
         <description><![CDATA[LIM TZE WANG

LIM TZE WANG
2h
LIM TZE WANG
BB15110347
System Analysis
Analysis of current system achievement

Analysis of a system’s user needs
Information gathering techniques
System’s analysis report
Accountant role in systems analysis 

System Design 

 User interface design
Output design
Input design
Security and control measures 
Accountant role in systems designing 

-



favorite_border
0


Add comment
NASRIAH BINTI NASIR

Nasriah Nasir
1h
NASRIAH BINTI NASIR
(BB15110444)
System Analysis
Analysis of current system achievement
Analysis of a system’s user needs

You can refer this link too : https://www.nap.edu/read/22281/chapter/6

4. Information gathering techniques 
As defined in the dictionary, information gathering is the act of collectinginformation from various sources through various means. In the literal sense,information gathering is a basic human skill necessary for undertaking basic human activities such as eating, sleeping, working etc. 

Managing information involves gathering and distributing necessary information and assimilating them on the project management activities and processes. The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:

Brainstorming: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.
Delphi technique: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.
Root cause analysis: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.
Interviewing: Stakeholders, participants, and experts are interviewed to identify risks. 
https://project-management-knowledge.com/definitions/i/information-gathering-techniques/ 
System’s analysis report

Accountant role in systems analysis 

System Design 

 User interface design
Output design
Input design
Security and control measures 
Accountant role in systems designing
favorite_border
0


Add comment
AMALINA BINTI NORAZAM

amalina norazam
1h
AMALINA BINTI NORAZAM
(BB15110086)

System Analysis
1)Analysis of current system achievement
2)Analysis of a system’s user needs
3)Information gathering techniques
4)System’s analysis report
5)Accountant role in systems analysis 

System Design
1)User interface design
2)Output design
3)Input design
4)Security and control measures 5)Accountant role in systems designing 
favorite_border
0


Add comment
Empty

Anonymous
8m
favorite_border
0


Add comment
CHORLELINA LABI (BB15110153)

Chorlelina
1m
CHORLELINA LABI (BB15110153)
System Analysis
 Systems analysis is a problem-solving method that involves looking at the wider system, breaking apart the parts, and figuring out how it works in order to achieve a particular goal. System analysis will improved performance and a feeling of achievement with quality information 
https://study.com/academy/lesson/systems-analysis-definition-example.html


Analysis of a system’s user needs
Information gathering techniques
System’s analysis report
Accountant role in systems analysis 

System Design 

 User interface design
Output design
Input design
Security and control measures 
Accountant role in systems designing
favorite_border
0


Add comment
JEEVANRAJ A/L RAJA BB15110270

Anonymous
20m
JEEVANRAJ A/L RAJA BB15110270
1. Analysis of current system achievement 
2. Analysis of system user needs
3.information gathering techniques
4 Accounting role in system analysis
5. system analysis report
 
System Design
 1. output design
2.user interface design
3.security and control measure
4. Accounting role in system designing
5.input design
favorite_border
0


Add comment
a

amalina norazam
1h
a
favorite_border
0


Add comment
NOR ASLINDA BINTI RUSLAN

Nor Aslinda Ruslan
18m
NOR ASLINDA BINTI RUSLAN
BB15110474
System Analysis
It is a process of collecting and interpreting facts, identifying the problems, and decomposition of a system into its components.
System analysis is conducted for the purpose of studying a system or its parts in order to identify its objectives. It is a problem solving technique that improves the system and ensures that all the components of the system work efficiently to accomplish their purpose.Analysis specifies what the system should do.
1. Analysis of current system achievement
2. Analysis of a system's user needs
3.information gathering techniques
4. System's analysis report
5. Accountant role in systems analysis

System Design
It is a process of planning a new business system or replacing an existing system by defining its components or modules to satisfy the specific requirements. Before planning, you need to understand the old system thoroughly and determine how computers can best be used in order to operate efficiently.
System Design focuses on how to accomplish the objective of the system.
1 User interface design
User interface (UI) design is the design of user interfaces for software or machines, such as the look of a mobile app, with a focus on ease of use and pleasurability for the user. UI design usually refers to the design of graphical user interfaces—but can also refer to others, such as natural and voice user interfaces.

Since software is intangible, the only way a user can control or interact with it is through a designed user interface. A well-designed user interface creates a user experience that the designer intended and/or a user experience that the user appreciates.

Many user interfaces are designed with a focus on usability and efficiency. Users should be able to achieve their goals as efficiently as possible, without focusing too much on the user interface itself. In that sense, a well-designed user interface becomes effectively invisible to those using it. In other words, they interact directly with the ‘reality’ the design portrays without reckoning on the point that, for example, thumbing button icons through the glass screens of their handheld devices is responsible for producing changes in what they see. However, usability and efficiency might not be the only measure of a well-designed user interface; a user interface might be designed to create a fun and pleasurable experience for users instead (e.g., in games).

At the other end of the spectrum, designers can—unethically—deliberately design user interfaces that are confusing—in order to trick users into purchasing or signing up for things they might not be interested in. These user interfaces are known as dark patterns. Examples of dark patterns include add-ons that are included by default (e.g., additional luggage allowance when booking air tickets), and intentionally complicated processes meant to deter users (e.g., long and confusing pages to unsubscribe from email newsletters).


2. Output design
 
System design gives the following outputs :
-Infrastructure and organizational changes for the proposed system.
-A data schema, often a relational schema.
-Metadata to define the tables/files and columns/data-items.
-A function hierarchy diagram or web page map that graphically describes the program structure.
-Actual or pseudocode for each module in the program.
-A prototype for the proposed system. 
3. Input design
System design takes the following inputs :
-Statement of work
-Requirement determination plan
-Current situation analysis
-Proposed system requirements including a conceptual data model, modified DFDs, and Metadata (data about data).
https://www.tutorialspoint.com/system_analysis_and_design/system_design.htm

4. Security and control measures
5. Accountant role in systems designing


favorite_border
0


Add comment
NG SYIE NIE (BB14110434

Anonymous
2h
NG SYIE NIE (BB14110434

System Analysis

1.      Analysis of current system achievement

The systems analyst needs to know the details of current system functions: the who (the people who are involved), what (the business activity), where (the environment in which the work takes place), when (the timing), and how (how the current procedures are performed) of the business under study. The analyst must then ask why the business uses the current system. There may be good reasons for doing business using the current methods, and these should be considered when designing any new system.
 
http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/

2.      Analysis of a system’s user needs

Understanding user requirements is an integral part of information systems design and is critical to the success of interactive systems. It is now widely understood that successful systems and products begin with an understanding of the needs and requirements of the users. As specified in the ISO 13407 standard (ISO, 1999), user-centred design begins with a thorough understanding of the needs and requirements of the users

The analyst will use various methods to pose and answer many questions concerning human-computer interaction (HCI), including questions such as, “What are the users’ physical strengths and limitations?” In other words, “What needs to be done to make the system audible, legible, and safe?” “How can the new system be designed to be easy to use, learn, and remember?” “How can the system be made pleasing or even fun to use?” “How can the system support a user’s individual work tasks and make them more productive in new ways?” In the information requirements phase of the SDLC, the analyst is striving to understand what information users need to perform their jobs. At this point the analyst is examining how to make the system useful to the people involved. How can the system better support individual tasks that need doing? What new tasks are enabled by the new system that users were unable to do without it? How can the new system be created to extend a user’s capabilities beyond what the old system provided? How can the analyst create a system that is rewarding for workers to use?
 http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89.2102&rep=rep1&type=pdf

3.      Information gathering techniques

The first step in user requirements analysis is to gather background information about the users and stakeholders and the processes that currently take place. The following methods may be adopted: Stakeholder analysis identifies all the users and stakeholders who may influence or be impacted by the system. This helps ensure that the needs of all those involved are taken into account. If required, the system is tested by them. User groups may include end users, supervisors, installers, and maintainers. Other stakeholders include recipients of output from the system, marketing staff, purchasers and support staff (Taylor, 1990). Stakeholder analysis identifies, for each user and stakeholder group, their main roles, responsibilities and task goals in relation to the system. One of the main issues is how to trade-off the competing needs of different stakeholder groups in the new system (see 4.5 Allocation of function and user cost-benefit analysis).

 

Secondary market research involves researching published sources such as research reports, census data, demographic information, that throw light upon the range of possible user markets. Websites representing special groups of users such as that for the Royal National Institute for the Blind (www.rnib.org.uk/digital) give information about the nature of the user population they represent (Mander & Smith, 2002).

 

Task analysis involves the study of what a user is required to do in terms of actions and/or cognitive processes to achieve a task. A detailed task analysis can be conducted to understand the current system, the information flows within it, the problems for people, and opportunities that indicate user needs. There are many variations of task analysis and notations for recording task activities. One of the most widely used is hierarchical task analysis, where high level tasks are de-composed into more detailed components and sequences. Another method creates a flow chart showing the sequence of human activities and the associated inputs and outputs (Ericsson 2001). Kirwan & Ainsworth (1992) provide a guide to the different task analysis methods, while Hackos & Redish (1998) explain some of the simpler methods for user interface design.

4.      System’s analysis report
A formal systems analysis report, prepared and presented to the steering committee, contains:
–reasons for system analysis
–scope of study
–problem identified with current system
–statement of user requirements
–resource implications
–recommendations

www.cengage.com/resource_uploads/downloads/1439078572_248443.pptx

5.      Accountant role in systems analysis 

The economic feasibility of proposed systems is of primary concern to accountants. Specifically, the accountant will ensure that:

• Only escapable costs are used in calculations of cost-savings benefits.

• Reasonable interest rates are used in measuring present values of cash flows.

• One-time and recurring costs are completely and accurately reported.

• Realistic useful lives are used in comparing competing projects.

• Intangible benefits are assigned reasonable financial values.

http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/


System Design 

1.       User interface design

User Interface Design is the design of websites, computers, appliances, machines, mobile communication devices, and software applications with the focus on the user’s experience and interaction. The goal of user interface design is to make the user’s interaction as simple and efficient as possible, in terms of accomplishing user goals—what is often called user-centered design.

https://www.freshtilledsoil.com/what-is-user-interface-design/

2.      Output design

Because useful output is essential to ensuring the use and acceptance of the information system, there are six objectives that the systems analyst tries to attain when designing output:

1.      Designing output to serve the intended purpose.

2.      Designing output to fit the user.

3.      Delivering the appropriate quantity of output.

4.      Making sure the output is where it is needed.

5.      Providing the output on time.

6.      Choosing the right output method.

http://www.w3computing.com/systemsanalysis/output-design-objectives/

3.      Input design

Users deserve quality output. The quality of system input determines the quality of system output. It is vital that input forms, displays, and interactive Web documents be designed with this critical relationship in mind. Well-designed input forms, displays, and interactive Web fill-in forms should meet the objectives of effectiveness, accuracy, ease of use, consistency, simplicity, and attractiveness. All these objectives are attainable through the use of basic design principles, the knowledge of what is needed as input for the system, and an understanding of how users respond to different elements of forms and displays.


Effectiveness means that input forms, input displays, and fill-in forms on the Web all serve specific purposes for users of the information system, whereas accuracy refers to design that ensures proper completion. Ease of use means that forms and displays are straightforward and require no extra time for users to decipher. Consistency means that all input forms, whether they are input displays or fill-in forms on the Web, group data similarly from one application to the next, whereas simplicity refers to keeping those same designs uncluttered in a manner that focuses the user’s attention. Attractiveness implies that users will enjoy using input forms because of their appealing design.


http://www.w3computing.com/systemsanalysis/designing-effective-input-intro/


 

4.      Security and control measures 

1.      Audit and Accountability


a)      Enable process auditing or accounting: Enable process auditing or accounting, which generates logs information about the creation of new processes and their system activity.


b)      Audit privilege escalation or change in privilege: Generate a log message whenever a user changes their level of privilege.


c)      Audit firewall denial: Generate a log message when the host-based firewall denies a network connection.


d)      Audit all significant application events: Log all significant application events.


e)      Write audit events to a separate system: System logs must be written to a remote system in such a way that they cannot be altered by any user on the system being logged.


2.      Configuration and Maintenance


a)      Follow advanced vendor security recommendations: This document cannot be comprehensive for all systems and applications available. Conform to best practices and recommendations outlined in vendor security whitepapers and documentation.


b)      Host-based and network-based firewalls: Systems must be protected by both a host-based and a network-based firewall that allows only those incoming connections necessary to fulfill the business need of that system.


c)      Configuration management process: Configuration changes must be regulated by a documented configuration and change management process.


d)      Partitioning: Systems may share hardware and resources only with other systems that have similar security requirements, regardless of their criticality classification. Systems which share similar security requirements have user communities of similar size and character, similar firewall profiles, and similar technical requirements. For example:


1.      Multiple systems of the same criticality may be aggregated together to share hardware and resources provided they have similar security requirements.


2.      High criticality systems may share hardware and resources with medium and low criticality systems provided that all systems meet the advanced systems Security Measures, and share similar security requirements.


3.      Additional Requirements


a)      Physical access: The system must reside in a secured, managed data-center.  


https://www.nyu.edu/about/policies-guidelines-compliance/policies-and-guidelines/data-and-system-security-measures.html


 

5.      Accountant role in systems designing

Accountants are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument. This function of designing AIS includes the design of managerial accounting information system to aid management in decision making processes.

Many accountants relinquished their traditional responsibilities to the new generation of computer professionals who were emerging in their organizations. Computer programmers, often with no accounting or business training, assumed full responsibility for the design of accounting information systems. As a result, many systems violated accounting principles and lacked necessary controls. Large system failures and computer frauds marked this period in accounting history. By the mid-1970s, in response to these problems, the accounting profession began to reassess the accountant’s professional and legal responsibilities for computer-based systems.

The design of the conceptual system involves specifying the criteria for identifying delinquent customers and the information that needs to be reported. The accountant determines the nature of the information required, its sources, its destination, and the accounting rules that need to be applied. The physical system is the medium and method for capturing and presenting the information. The computer professionals determine the most economical and effective technology for accomplishing the task. Hence, systems design should be a collaborative effort. Because of the uniqueness of each system and the susceptibility of systems to serious error and even fraud, the accountant’s involvement in systems design should be pervasive.

http://bepls.com/beplsoctober2015/19.pdf

 

 

 
favorite_border
0


Add comment
ASMAUL HUSNA NURDIN BB15110106

ASMAUL HUSNA BINTI NURDIN FPEP
2h
ASMAUL HUSNA NURDIN BB15110106
favorite_border
0


Add comment
ASMAUL HUSNA

ASMAUL HUSNA BINTI NURDIN FPEP
2h
ASMAUL HUSNA 
favorite_border
0


Add comment
NOR SYUHADA BINTI ROCKY(BB15110485)

Nor Syuhada Binti Rocky
1h
NOR SYUHADA BINTI ROCKY(BB15110485)
System Analysis
1. Analysis of current system achievement
2. Analysis of a system's user needs
3.information gathering techniques
4. System's analysis report
5. Accountant role in systems analysis

    
System Design

User interface design
Output design
Input design
Security and control measures
Accountant role in systems designing
favorite_border
0


Add comment
NURUL HIDAYAH BINTI KHAIRONI(BB15110589)

nurul hidayah khaironi
1m
NURUL HIDAYAH BINTI KHAIRONI(BB15110589)
Lecture 5: System Analysis & Design
Systems Analysis and Design is an active field in which analysts repetitively learn new approaches and different techniques for building the system more effectively and efficiently. The primary objective of systems analysis and design is to improve organizational systems. 
(https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf)


[System Analysis]
It is a process of collecting and interpreting facts, identifying the problems, and decomposition of a system into its components. System analysis is conducted for the purpose of studying a system or its parts in order to identify its objectives. It is a problem solving technique that improves the system and ensures that all the components of the system work efficiently to accomplish their purpose. Analysis specifies what the system should do. 

1. Analysis of current system achievement

2. Analysis of a system’s user needs

3. Information gathering techniques
The main aim of fact finding techniques is to determine the information requirements of an organization used by analysts to prepare a precise SRS understood by user. Ideal SRS Document should: 
 be complete, Unambiguous, and Jargon-free. 
 specify operational, tactical, and strategic information requirements.  solve possible disputes between users and analyst.
 use graphical aids which simplify understanding and design. There are various information gathering techniques: 
1)Interviewing
2)Questionnaires
3)Reviews of record, procedures and forms
4)Observation
5)Joint Application Development(JAD)
6)Secondary research or background reading

4. System’s analysis report

5.Accountant role in systems analysis 

[System Design]
It is a process of planning a new business system or replacing an existing system by defining its components or modules to satisfy the specific requirements. Before planning, you need to understand the old system thoroughly and determine how computers can best be used in order to operate efficiently. System Design focuses on how to accomplish the objective of the system.

1. User interface design

2. Output design

3. Input design

4. Security and control measures 

5. Accountant role in systems designing
favorite_border
0


Add comment
SUHAILAH BINTI JALIL (BB15110725)

Suhailah binti Jalil
2h
SUHAILAH BINTI JALIL (BB15110725)

 
System Analysis
Analysis of current system achievement
Analysis of a system’s user needs
Information gathering techniques
System’s analysis report
Accountant role in systems analysis 

System Design 

 User interface design
Output design
Input design
Security and control measures 
Accountant role in systems designing 
favorite_border
0


Add comment
ROSITA BINTI DARWIS (BB15110639)

ROSITA BINTI DARWIS FPEP
2h
ROSITA BINTI DARWIS (BB15110639)
System Analysis
Analysis of current system achievement : 
Analysis of a system’s user needs :
Information gathering techniques
System’s analysis report
Accountant role in systems analysis 

System Design 

 User interface design
Output design
Input design
Security and control measures 
Accountant role in systems designing
favorite_border
0


Add comment
ASMAUL HUSNA BINTI NURDIN

ASMAUL HUSNA BINTI NURDIN FPEP
2h
ASMAUL HUSNA BINTI NURDIN 
favorite_border
0


Add comment
ASMAUL HUSNA BINTI NURDIN BB151101

ASMAUL HUSNA BINTI NURDIN FPEP
2h
ASMAUL HUSNA BINTI NURDIN BB151101
favorite_border
0


Add comment
ASMAUL HUSNA BINTI NURDIN BB15110106

ASMAUL HUSNA BINTI NURDIN FPEP
2h
ASMAUL HUSNA BINTI NURDIN BB15110106


ecture 5:
undefined
favorite_border
0


Add comment
NURUL HIDAYAH BINTI ABDUL SUHUD BB15110588

NURUL HIDAYAH ABDUL SUHUD
2h
NURUL HIDAYAH BINTI ABDUL SUHUD BB15110588
System Analysis
Analysis of current system achievement
Analysis of a system’s user needs
Information gathering techniques
System’s analysis report
Accountant role in systems analysis 

System Design 

 User interface design
Output design
Input design
Security and control measures 
Accountant role in systems designing

favorite_border
0


Add comment
MARIYANI BINTI SIDIRMAN BB

Anonymous
2h
MARIYANI BINTI SIDIRMAN BB
favorite_border
0


Add comment
MARIYANI BINTI SIDIRMAN BB15110371)

Anonymous
2h
MARIYANI BINTI SIDIRMAN BB15110371)
favorite_border
0


Add comment
MARIYANI BINTI SIDIRMAN (BB15110371)

Anonymous
2h
MARIYANI BINTI SIDIRMAN (BB15110371)

System Analysis
1. Analysis of current system achievement



favorite_border
0


Add comment
NURFATIN AFIFAH BINTI ABDUL AZIZ (BB15110558)

Nurfatin Afifah Binti Abdul Aziz
2h
NURFATIN AFIFAH BINTI ABDUL AZIZ (BB15110558)
System Analysis
 Analysis of current system achievement
Analysis of a system’s user needs
Information gathering techniques
System’s analysis report
Accountant role in systems analysis 

System Design 
 User interface design
Output design
Input design
Security and control measures 
Accountant role in systems Designing









favorite_border
0


Add comment
System Analy

Anonymous
2h
 System Analysis
Analysis of current system achievement
Analysis of a system’s user needs
Information gathering techniques
System’s analysis report
Accountant role in systems analysis 

System Design 

 User interface design
Output design
Input design
Security and control measures 
Accountant role in systems designing
favorite_border
0


Add comment
AMINA BINTI RIDDUAN

Amina Ridduan
2h
AMINA BINTI RIDDUAN
q
favorite_border
0


Add comment
NORATNA BINTI AWANG ASAL (BB15110493)

Anonymous
1m
NORATNA BINTI AWANG ASAL (BB15110493)
System Analysis 
1. Analysis of current system achievement
2. Analysis of a system’s user needs
3. Information gathering techniques
Managing information involves gathering and distributing necessary information and assimilating them on the project management activities and processes. The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:

Brainstorming: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.
Delphi technique: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.
Root cause analysis: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.
Interviewing: Stakeholders, participants, and experts are interviewed to identify risks.


4. System’s analysis report
The report should be as long as necessary to record fully (1) what was done by the project team, (2) what the team's findings are, and (3) what recommendations, including further courses of actions, are being made by the project team.
https://www.ischool.utexas.edu/~wyllys/SAEMaterials/stylesysanlrpt.html
5. Accountant role in systems analysis 
 
First, accountants are users. All systems that process financial transactions impact the accounting function in some way. Like all users, accountants must provide a clear picture of their problems and needs to the systems professional. For example, accountants must specify accounting techniques to be used; internal control requirements, such as audit trails; and special algorithms, such as depreciation models.

Second, accountants participate in systems development as members of the development team. Their involvement often extends beyond the development of strictly accounting information systems applications. Systems that do not process financial transactions may still draw on accounting data. The accountant may be consulted to provide advice or to determine if the proposed system constitutes an internal control risk.

Third, accountants are involved in systems development as auditors. Accounting information systems must be auditable. Some computer audit techniques require special features that must be designed into the system. The auditor/accountant has a stake in such systems and must be involved early in their design. 
http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/
System Design 
1. User interface design
User Interface (UI) Design focuses on anticipating what users might need to do and ensuring that the interface has elements that are easy to access, understand, and use to facilitate those actions. UI brings together concepts from interaction design, visual design, and information architecture.
2.Output design
The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.
https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm
3. Input design
input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.

Therefore, the quality of system input determines the quality of system output. Well designed input forms and screens have following properties −

It should serve specific purpose effectively such as storing, recording, and retrieving the information.

It ensures proper completion with accuracy.

It should be easy to fill and straightforward.

It should focus on user’s attention, consistency, and simplicity.

All these objectives are obtained using the knowledge of basic design principles regarding −

What are the inputs needed for the system?

How end users respond to different elements of forms and screens.
https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm

4.Security and control measures
5. Accountant role in systems designing
 The accountant plays an important role in the conceptual design of the system. He or she must recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood. These issues need not be specified in detail at this point, but they should be recognized as items to be addressed during the construct phase of the system. Furthermore, the auditability of a system depends in part on its design characteristics. Some computer auditing techniques require systems to be designed with built-in audit features. Such features require resources and need to be considered at conceptual design.
http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/


favorite_border
0


Add comment
DARYUNI BINTI DAFRI

Daryuni dafri
1m
DARYUNI BINTI DAFRI 
(BB15110173)
 
System Analysis
Analysis of current system achievement
 
Analysis is a detailed study of the various operations performed by a system and 
their relationships within and outside of the 
system. One aspect of analysis is defining the boundaries of the system and 
determining whether or not a candidate system
 should consider other related systems. 
During analysis, data are collected on the available files, decision points, and transactions 
handled by the present system. Data flow diag
rams interviews, on – site observations, and 
questionnaires are examples of the analysis t
ools. The interviews is a commonly used tool 
in analysis, it requires special skills and sensitivity to the subjects being interviewed. Bias 
in data collection and interpretation can be a problem. Training, experience, and common 
sense are required for collection of the information needed to do the analysis 
Analysis of a system’s user needs
Information gathering techniques
System’s analysis report
Accountant role in systems analysis 

System Design 

 User interface design
Output design
Input design
Security and control measures 
Accountant role in systems designing 


favorite_border
0


Add comment
SYSTEM ANALYSIS

Jack Hazlyne Zim
2h
SYSTEM ANALYSIS
1. Analysis of current system achievement
2. Analysis of system's user needs
3. Information gathering techniques
4. System's analysis report
Accountant role in system analysis

SYSTEM DESIGN
1. User interface design
2. Output design
3. Input design
4. Security and control measures
5. Accountant role in system designing
favorite_border
0


Add comment
Siti Fazwalina Binti Wahimin (BB15110684)

Anonymous
2h
Siti Fazwalina Binti Wahimin (BB15110684)
SYSTEM ANALYSIS
1.Analysis of current system achievement
2. Analysis of a system's user needs
3. Information gathering techniques
4. System's analysis report
5. Accountant role in systems analysis

SYSTEM DESIGN




favorite_border
0


Add comment
SYSTEM ANALYSIS

Junikolee Toingin
3h
SYSTEM ANALYSIS 

SYSTEM ANALYSIS
1. Analysis of current system achievement
2. Analysis of system's user needs
3. Information gathering techniques.
4. System's analysis report
5. Accountant role in system analysis

SYSTEM DESIGN
1. User interface design
2. Output design
3. Input design
4. Security and control measures
5. Accountant role in system designing


favorite_border
0


Add comment
Siti Noorazura Binti Ramsa (BB15110691)

Anonymous
2h
Siti Noorazura Binti Ramsa (BB15110691)
System Analysis
1. Analysis of current system achievement
2. Analysis of a system's user needs
3. Information gathering techniques

 DEFINITION
The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:

Brainstorming: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.
Delphi technique: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.
Root cause analysis: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.
Interviewing: Stakeholders, participants, and experts are interviewed to identify risks. 

https://project-management-knowledge.com/definitions/i/information-gathering-techniques/

4. System's analysis report
https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php
5.Accountant role in systems analysis

First, accountants are users. All systems that process financial transactions impact the accounting function in some way. Like all users, accountants must provide a clear picture of their problems and needs to the systems professional. For example, accountants must specify accounting techniques to be used; internal control requirements, such as audit trails; and special algorithms, such as depreciation models.
 Second, accountants participate in systems development as members of the development team. Their involvement often extends beyond the development of strictly accounting information systems applications. Systems that do not process financial transactions may still draw on accounting data. The accountant may be consulted to provide advice or to determine if the proposed system constitutes an internal control risk.
 Third, accountants are involved in systems development as auditors. Accounting information systems must be auditable. Some computer audit techniques require special features that must be designed into the system. The auditor/accountant has a stake in such systems and must be involved early in their design.  


System Design 
1. User interface design
2.Output design
3.Input design
4.Security and control measures
5.Accountant role in systems designing

favorite_border
0


Add comment
Lecture 5:

SHARIFAH MILDA BINTI AMIRUL -
4h
Lecture 5:
System Analysis
Analysis of current system achievement
Analysis of a system’s user needs
Information gathering techniques
System’s analysis report
Accountant role in systems analysis 

System Design 

 User interface design
Output design
Input design
Security and control measures 
Accountant role in systems designing



favorite_border
0


Add comment
]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 05:13:50 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248369131</guid>
      </item>
      <item>
         <title>LAILA NAJWA BINTI SHAHARUDDIN BB15110317</title>
         <author>lailanajwa94</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248370886</link>
         <description><![CDATA[<div>&nbsp;</div><div><strong>System Analysis<br></strong>1. Analysis of current system achievement<br>- <strong>system analysis: </strong>"the process of studying a procedure or <a href="https://en.wikipedia.org/wiki/Business">business</a> in order to identify its goals and purposes and create <a href="https://en.wikipedia.org/wiki/System">systems</a> and procedures that will achieve them in an efficient way". Another view sees system analysis as a <a href="https://en.wikipedia.org/wiki/Problem-solving">problem-solving</a> technique that breaks down a system into its component pieces for the purpose of the studying how well those component parts work and interact to accomplish their purpose.<br><br> The purpose of <strong>current systems analysis</strong> technique is to identify shortcomings and issues with <strong>current systems</strong>. It is used to assess the usefulness, usability, and overall user satisfaction with the <strong>current systems</strong> to facilitate decision making concerning the <strong>current systems</strong>' strategic and tactical viability. <br> <a href="https://www.projectmanagement.com/process/popup.cfm?ID=23401">https://www.projectmanagement.com/process/popup.cfm?ID=23401 </a><br>2. Analysis of a system’s user needs.<br>-&nbsp; The aim of our user-focused tools and methods is to provide a clear understanding of requirements as an early input to development projects. We help focus design work on those issues that are central to the success of a product or system in the eyes of the end-users.</div><div>Usability Partners is experienced with a range of requirements gathering and analysis techniques - we select those most appropriate to a given project situation. Whether end-users are professionals or consumers, located locally or around the globe, there are techniques for gathering their needs.</div><div>Typical requirements gathering and analysis methods include:</div><ul><li><em>Surveys</em> – both open-ended and focused surveys, conducted electronically or on paper.</li><li><em>Interviews</em> – typically conducted face-to-face, but also over the telephone if deemed more appropriate.</li><li><em>Focus groups</em> – whilst being poorly suited to evaluating a product, focus groups are useful for discussing possible user requirements and brainstorming ideas.</li><li><em>Field studies </em>– observing the end-user situation and the environment in which a new product or system will be used is often extremely useful in understanding user needs.</li><li><em>Evaluation of an existing product</em> – provides a range of useful information (even competitor products can be tested). Usability evaluation reveals and clarifies good and bad aspects of current solutions - valuable input to new design work.</li><li><em>Task analysis</em> – a deeper analysis of users work with a system, useful for analysing how user's work tasks should be supported by functionality in a system.</li><li><em>User personas and usage scenarios</em> – concrete and illustrative data about typical users, their characteristics, usage situation, tasks and goals. Particularly useful in supporting early user interface design work.</li><li><em>Formulation of usability goals and overall design criteria</em> – help focus and steer the design process, supporting the evaluation of early concepts, prototypes and final designs.&nbsp;</li></ul><div><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a><br><br>3. Information gathering techniques</div><div>&gt; <strong>through interviews</strong><br> - <em>Depth interviews:</em> conversation is guided largely by feelings and interest of the person being interviewed.<br>- <em>&nbsp;Structured interviews: </em>useful after a depth interview for obtaining answers to a specific set of questions.<br>&gt; <strong>through questionnaires<br></strong>&nbsp;- <em>Open-ended questionnaires: </em>persons provide written answers to general rather than specific questions.<br>&nbsp;- <em>&nbsp;Closed-ended questionnaires: </em>&nbsp;use for routine situations or when a large number of similar individuals would be questioned.<br><br>4. System’s analysis report</div><div>- the report should organize and document the first three phases of analysis. Some key elements of the report include:<br>&gt; description of the overall problems in subsystem being studied.<br>&gt; recommendations for improving existing system or design of new system.<br>&gt; overall cost budget and timetable for project to date.<br><br>5. Accountant role in systems analysis&nbsp;<br>-&nbsp; The creation of an information system consumes significant resources and has financial resource implications.&nbsp;</div><div>- The quality of accounting information systems and their output rests directly on the SDLC activities that produce them.&nbsp;<br>&nbsp;&gt; As end users who must provide a clear picture of their problems and needs.</div><div>&gt; As members of the development team.&nbsp;</div><div>&gt; As auditors who must ensure that the system is designed with appropriate internal controls and computer audit techniques&nbsp;</div><div><strong>SYSTEM DESIGN<br></strong>1. User interface design<br>- User Interface Design is the design of websites, computers, appliances, machines, mobile communication devices, and software applications with the focus on the user’s experience and interaction. The goal of user interface design is to make the user’s interaction as simple and efficient as possible, in terms of accomplishing user goals—what is often called user-centered design.<br><a href="https://www.freshtilledsoil.com/what-is-user-interface-design/">https://www.freshtilledsoil.com/what-is-user-interface-design/</a><br><br>2. Output design<br>-&nbsp; The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.</div><div>The objectives of input design are−</div><ul><li>To develop output design that serves the intended purpose and eliminates the production of unwanted output.</li><li>To develop the output design that meets the end users requirements.</li><li>To deliver the appropriate quantity of output.</li><li>To form the output in appropriate format and direct it to the right person.</li><li>To make the output available on time for making good decisions.&nbsp;</li></ul><div>&nbsp;</div><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm&nbsp;</a></div><div><br>3. Input design<br>-&nbsp; In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.<br><br></div><div>Therefore, the quality of system input determines the quality of system output. Well designed input forms and screens have following properties −</div><ul><li>It should serve specific purpose effectively such as storing, recording, and retrieving the information.</li><li>It ensures proper completion with accuracy.</li><li>It should be easy to fill and straightforward.</li><li>It should focus on user’s attention, consistency, and simplicity.</li><li>All these objectives are obtained using the knowledge of basic design principles regarding −<ul><li>What are the inputs needed for the system?</li><li>How end users respond to different elements of forms and screens.</li></ul></li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a></div><div><br>4. Security and control measures<br>-&nbsp; <strong>Security controls</strong> are safeguards or <a href="https://en.wikipedia.org/wiki/Countermeasure_(computer)">countermeasures</a> to avoid, detect, counteract, or minimize <a href="https://en.wikipedia.org/wiki/Security_risk">security</a> <a href="https://en.wikipedia.org/wiki/Risks">risks</a> to physical property, information, computer systems, or other assets.<br><br></div><div>They can be classified by several criteria. For example, according to the time that they act, relative to a security incident:</div><ul><li>Before the event, <strong>preventive controls</strong> are intended to prevent an incident from occurring e.g. by locking out unauthorized intruders;</li><li>During the event, <strong>detective controls</strong> are intended to identify and characterize an incident in progress e.g. by sounding the intruder alarm and alerting the security guards or police;</li><li>After the event, <strong>corrective controls</strong> are intended to limit the extent of any damage caused by the incident e.g. by recovering the organization to normal working status as efficiently as possible.</li></ul><div>According to their nature, for example:</div><ul><li><strong>Physical controls</strong> <em>e.g.</em> fences, doors, locks and fire extinguishers;</li><li><strong>Procedural controls</strong> <em>e.g.</em> incident response processes, management oversight, security awareness and training;</li><li><strong>Technical controls</strong> <em>e.g.</em> user authentication (login) and logical access controls, antivirus software, firewalls;</li><li><strong>Legal and regulatory or compliance controls</strong> <em>e.g.</em> privacy laws, policies and clauses.&nbsp;</li></ul><div><a href="https://en.wikipedia.org/wiki/Security_controls">https://en.wikipedia.org/wiki/Security_controls</a><br><br>5. Accountant role in system designing<br>-&nbsp; <a href="http://www.accountantnextdoor.com/qualified-accountant-who-is-a-qualified-accountant/">Accountants</a> are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument. This function of designing AIS includes the design of <a href="http://www.accountantnextdoor.com/managerial-accounting-%e2%80%93-what-you-must-know-as-a-management-accountant/">managerial accounting</a> information system to aid management in <a href="http://www.accountantnextdoor.com/decision-making-process-what-every-accountant-must-know-about-making-decision/">decision making processes</a>. <br><a href="http://www.accountantnextdoor.com/accountants%E2%80%99-role-in-the-accounting-information-system/">http://www.accountantnextdoor.com/accountants%E2%80%99-role-in-the-accounting-information-system/</a></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 05:31:42 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248370886</guid>
      </item>
      <item>
         <title>NUR AZLINNIE RUSLAN (BB15110524)</title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248371668</link>
         <description><![CDATA[<div>&nbsp;</div><div>a) <strong>System Analysis</strong></div><ol><li><strong><em>Analysis of current system achievement</em></strong></li></ol><div>Current systems analysis is to identify shortcomings and issues with current systems. It is used to assess the usefulness, usability, and overall user satisfaction with the current systems to facilitate decision making concerning the current systems’ strategic and tactical viability. Current systems analysis technique is used to evaluate the degree of support provided by current systems to the business activities of the enterprise. Assessments of user and technical satisfaction are performed and data, procedures and problems are analyzed. <br><a href="https://www.projectmanagement.com/process/popup.cfm?ID=23401">https://www.projectmanagement.com/process/popup.cfm?ID=23401</a><br><br><strong><em>2. Analysis of a system’s user needs</em></strong></div><div>the users must understand their needs by specified user requirement, it is also requires a proper understanding of both user and organisational requirements by&nbsp; integrate and balance the two in the specification process. Also, avoid over-reliance on internally generated requirements (what its believed that users want), as opposed to data from end-user requirements studies (what users actually need). <br><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a><br><br>3. <strong><em>Information gathering techniques</em></strong></div><ul><li><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.</li><li><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.</li><li><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.</li><li><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks.&nbsp;</li></ul><div><a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a><br><br>4. <strong><em>System’s analysis report</em></strong></div><div>The system analysis report is intended for all the project's major stakeholders: the client, the academic supervisors and the development team.<br>-&nbsp; this report will highlight the system vision by expanding on the project description, system capabilities and business benefits. <br><a href="https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php">https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php</a><br><br>5. <strong><em>Accountant role in systems analysis.</em></strong></div><div>- AS DESIGNERS<strong><br></strong>&nbsp;design of&nbsp; managerial accounting, information system to aid management in decision making process.&nbsp;</div><div>AS IMPLEMENTERS</div><div>&nbsp;ensure that AIS designed are actually implemented. It is not enough to just have procedures in place, implementation and enforcement is very important.&nbsp;</div><div>AS AUDITORS</div><div>Accountants audit the already ‘acclaimed’ AIS to ensure that what is claimed to have been implemented is actually followed.&nbsp;</div><div>AS OWNERS <br>As accountants gets more involved in the overall decision making in the business angle, a lot of accountants are now being classified as users of accounting information system. <br><a href="http://www.accountantnextdoor.com/accountants%E2%80%99-role-in-the-accounting-information-system/">http://www.accountantnextdoor.com/accountants%E2%80%99-role-in-the-accounting-information-system/</a><br><strong><br>b) System Design&nbsp;</strong></div><ol><li><strong><em>&nbsp;User interface design</em></strong></li></ol><div>User interface (UI) design is the design of user interfaces for software or machines, such as the look of a mobile app, with a focus on <em>ease of use</em> and <em>pleasurability</em> for the user. UI design usually refers to the design of graphical user interfaces—but can also refer to others, such as natural and voice user interfaces. <br><a href="https://www.interaction-design.org/literature/topics/ui-design">https://www.interaction-design.org/literature/topics/ui-desig</a>n<br><br>2. <strong><em>Output design</em></strong></div><div>&nbsp;The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.&nbsp;</div><ul><li>To develop output design that serves the intended purpose and eliminates the production of unwanted output.</li><li>To develop the output design that meets the end users requirements</li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.ht</a>m<br><br>3. <strong><em>Input design</em></strong></div><div>&nbsp;input is the raw data that is processed to produce output.&nbsp;</div><ul><li>To design data entry and input procedures</li><li>To design source documents for data capture or devise other data capture methods</li><li>To use validation checks and develop effective input controls.<br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a></li></ul><div><br></div><div><strong><em>4. Security and control measures</em></strong>&nbsp;</div><div>Backup</div><ul><li>Regular backup of databases daily/weekly depending on the time criticality and size.</li></ul><div>Physical Access Control to Facilities&nbsp;<br>- fingerprint, ID cards</div><div>Using Logical or Software Control</div><ul><li>Password system, Encrypting sensitive data/programs.&nbsp;</li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm</a><br><br><strong>5</strong>. <strong><em>Accountant role in systems designing</em></strong></div><div>-The accountant plays an important role in the conceptual design of the system. <br>-must recognize control implications of each alternative design <br>-ensure that accounting conventions and legal requirements are understood.<br>&nbsp;-should be recognized as items to be addressed during the construct phase of the system. <br>- considered some computer auditing techniques require systems to be designed with built-in audit features.<br><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 05:40:12 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248371668</guid>
      </item>
      <item>
         <title>NUR SUHAIKAH BINTI SIMAN</title>
         <author>nursuhaikahsiman</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248372072</link>
         <description><![CDATA[<div>(<strong>BB15110546)<br></strong> </div><div><strong><mark>System Analysis</mark></strong><strong><br></strong> It is a process of collecting and interpreting facts, identifying the problems, and decomposition of a system into its components.<br><br></div><div>System analysis is conducted for the purpose of studying a system or its parts in order to identify its objectives. It is a problem solving technique that improves the system and ensures that all the components of the system work efficiently to accomplish their purpose. <br><br><a href="https://www.tutorialspoint.com/system_analysis_and_design/index.htm">https://www.tutorialspoint.com/system_analysis_and_design/index.htm</a><br><strong><em><mark>1. Analysis of current system achievement</mark></em></strong></div><div>The systems analyst needs to know the details of current system functions: the who (the people who are involved), what (the business activity), where (the environment in which the work takes place), when (the timing), and how (how the current procedures are performed) of the business under study. The analyst must then ask why the business uses the current system. There may be good reasons for doing business using the current methods, and these should be considered when designing any new system.<br><br><a href="http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/">http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/</a><br><br><strong><em><mark>2. Analysis of a system’s user needs</mark></em></strong><strong><br></strong>The systems analyst undertakes involves analyzing system needs. Special tools and techniques help the analyst make requirement determinations. <br><strong><br></strong>The systems analyst prepares a systems proposal that summarizes what has been found out about the users, usability, and usefulness of current systems; provides cost-benefit analyses of alternatives; and makes recommendations on what (if anything) should be done. <br><br>If one of the recommendations is acceptable to management, the analyst proceeds along that course. Each systems problem is unique, and there is never just one correct solution. <br><br><a href="http://www.w3computing.com/systemsanalysis/analyzing-system-needs-sdlc/">http://www.w3computing.com/systemsanalysis/analyzing-system-needs-sdlc/</a><br><strong><br></strong><strong><em><mark>3. Information gathering techniques</mark></em></strong><strong><br></strong>The main purpose of gathering information is to determine the information requirements of an organization. Information requirements are often not stated precisely by management. It is the analyst’s responsibility to prepare a precise Systems Requirements Specifications (SRS), which is easily understood (SRS) by users, as SRS document is a vital document before starting a project.<br><br>Information can be gathered by interviewing top-level management, middle level management and operational staff. Besides Interviews group discussions also help the analyst to gather information. It is not possible to obtain all information in a single interview, more than one interview is thus required. <strong><br><br></strong>Other methods of information search are: <br>� Systems used in other similar organization <br>� Observe workflow in workplace � Repository of systems developed for similar organizations available. <br><strong><br></strong><a href="http://nptel.ac.in/courses/106108103/pdf/Lecture_Notes/LNm3.pdf"><strong>http://nptel.ac.in/courses/106108103/pdf/Lecture_Notes/LNm3.pdf</strong></a><strong><br><br></strong><strong><em><mark>4. System’s analysis report</mark></em></strong></div><div>A formal systems analysis report, prepared and presented to the steering committee, contains: </div><div>-reasons for system analysis </div><div>-scope of study </div><div>-problem identified with current system </div><div>-statement of user requirements </div><div>-resource implications </div><div>recommendations <br><br></div><div><a href="http://www.cengage.com/resource_uploads/downloads/1439078572_248443.pptx">www.cengage.com/resource_uploads/downloads/1439078572_248443.pptx</a><strong><br><br></strong><strong><em><mark>5. Accountant role in systems analysis </mark></em></strong><strong><br></strong> </div><div>System analysis is an intellectual process that is commingled with fact gathering. The accountant’s expertise makes them important players in the design of a good well-controlled system: </div><div>�Internal control standards </div><div>�Audit trail requirements </div><div>�External reporting requirements </div><div>�Double entry system <br><br></div><div><a href="http://webcache.googleusercontent.com/search?q=cache:tjq6YSS-IKgJ:willie-kuku.doomby.com/medias/files/grp-3.pptx+&amp;cd=4&amp;hl=en&amp;ct=clnk&amp;gl=my">http://webcache.googleusercontent.com/search?q=cache:tjq6YSS-IKgJ:willie-kuku.doomby.com/medias/files/grp-3.pptx+&amp;cd=4&amp;hl=en&amp;ct=clnk&amp;gl=my</a><br><strong><br></strong><strong><mark>System Design</mark></strong><strong> <br></strong> It is a process of planning a new business system or replacing an existing system by defining its components or modules to satisfy the specific requirements. Before planning, you need to understand the old system thoroughly and determine how computers can best be used in order to operate efficiently.<br><br></div><div>System Design focuses on how to accomplish the objective of the system. <br><br><a href="https://www.tutorialspoint.com/system_analysis_and_design/index.htm">https://www.tutorialspoint.com/system_analysis_and_design/index.htm</a><br><br><strong><em><mark>1. User interface design</mark></em></strong></div><div>User interface (UI) design is the design of user interfaces for software or machines, such as the look of a mobile app, with a focus on <em>ease of use</em> and <em>pleasurability</em> for the user. UI design usually refers to the design of graphical user interfaces—but can also refer to others, such as natural and voice user interfaces. <br><br><a href="https://www.interaction-design.org/literature/topics/ui-design">https://www.interaction-design.org/literature/topics/ui-design</a><br><br><strong><em><mark>2. Output design</mark></em></strong></div><div>The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.<br><br></div><div>The objectives of output design are </div><ul><li>To develop output design that serves the intended purpose and eliminates the production of unwanted output.</li><li>To develop the output design that meets the end users requirements.</li><li>To deliver the appropriate quantity of output.</li><li>To form the output in appropriate format and direct it to the right person.</li><li>To make the output available on time for making good decisions.</li></ul><div>Types of outputs :</div><div>1.External Outputs<br>2.Internal outputs<br><br><a href="https://www.tutorialspoint.com/system_analysis_and_design/index.htm">https://www.tutorialspoint.com/system_analysis_and_design/index.htm</a><br><br><strong><em><mark>3.Input design</mark></em></strong></div><div>In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.<br><br></div><div>Therefore, the quality of system input determines the quality of system output. Well designed input forms and screens have following properties −<br><br></div><ul><li>It should serve specific purpose effectively such as storing, recording, and retrieving the information.<br><br></li><li>It ensures proper completion with accuracy.<br><br></li><li>It should be easy to fill and straightforward.<br><br></li><li>It should focus on user’s attention, consistency, and simplicity.<br><br></li><li>All these objectives are obtained using the knowledge of basic design principles regarding −<br><br><ul><li>What are the inputs needed for the system?<br><br></li><li>How end users respond to different elements of forms and screens.</li></ul></li></ul><div><br></div><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/index.htm">https://www.tutorialspoint.com/system_analysis_and_design/index.htm</a><br><br></div><div><strong><em><mark>4.Security and control measures</mark></em></strong></div><div><strong>a) Security</strong></div><div>System security refers to protecting the system from theft, unauthorized access and modifications, and accidental or unintentional damage. In computerized systems, security involves protecting all the parts of computer system which includes data, software, and hardware. Systems security includes system privacy and system integrity.</div><ul><li><strong>System privacy</strong> deals with protecting individuals systems from being accessed and used without the permission/knowledge of the concerned individuals.</li><li><strong>System integrity</strong> is concerned with the quality and reliability of raw as well as processed data in the system.<br><br></li></ul><div><strong>b) Control Measures</strong></div><div>There are variety of control measures which can be broadly classified as follows −<br><br></div><div>1) Backup<br><br></div><ul><li>Regular backup of databases daily/weekly depending on the time criticality and size.</li><li>Incremental back up at shorter intervals.</li><li>Backup copies kept in safe remote location particularly necessary for disaster recovery.</li><li>Duplicate systems run and all transactions mirrored if it is a very critical system and cannot tolerate any disruption before storing in disk.</li></ul><div><br></div><div>2) Physical Access Control to Facilities<br><br></div><ul><li>Physical locks and Biometric authentication. For example, finger print</li><li>ID cards or entry passes being checked by security staff.</li><li>Identification of all persons who read or modify data and logging it in a file.</li></ul><div><br>3) Using Logical or Software Control</div><ul><li>Password system.</li><li>Encrypting sensitive data/programs.</li><li>Training employees on data care/handling and security.</li><li>Antivirus software and Firewall protection while connected to internet. </li></ul><div><br></div><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/index.htm">https://www.tutorialspoint.com/system_analysis_and_design/index.htm</a> <br><br><strong><em><mark>5. Accountant role in systems designing </mark></em></strong></div><div> The accountant plays an important role in the conceptual design of the system. He or she must recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood. These issues need not be specified in detail at this point, but they should be recognized as items to be addressed during the construct phase of the system. <br><br>Furthermore, the auditability of a system depends in part on its design characteristics. Some computer auditing techniques require systems to be designed with built-in audit features. Such features require resources and need to be considered at conceptual design. <br><br><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 05:45:33 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248372072</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248372377</link>
         <description><![CDATA[It is to identify shortcomings and issues with current systems. It is used to assess the usefulness, usability, and overall user satisfaction with the current systems to facilitate decision making concerning the current systems’ strategic and tactical viability.]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 05:48:57 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248372377</guid>
      </item>
      <item>
         <title>JANANI VENGU</title>
         <author>janani_vengu</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248372604</link>
         <description><![CDATA[<div>1</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 05:50:49 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248372604</guid>
      </item>
      <item>
         <title>PUSPHA DEWI A/P BALA KRISHNAN(BB15110613)</title>
         <author>pusphakrishnan</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248375216</link>
         <description><![CDATA[]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/221606919/042972657bf5dedc47b047d2cfeb5f8a/SYSTEM_ANALYSIS___DESIGN_PADLET.docx" />
         <pubDate>2018-04-04 06:09:13 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248375216</guid>
      </item>
      <item>
         <title>Tan Siok Hui BB15110739</title>
         <author>bb15110739</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248380446</link>
         <description><![CDATA[<div><strong>System Analysis</strong><br><strong>1.Analysis of Current System Achievement <br>-</strong>Current systems analysis technique is used to evaluate the degree of support provided by current systems to the business activities of the enterprise. Assessments of user and technical satisfaction are performed and data, procedures and problems are analyzed.The purpose of current systems analysis technique is to identify shortcomings and issues with current systems. It is used to assess the usefulness, usability, and overall user satisfaction with the current systems to facilitate decision making concerning the current systems’ strategic and tactical viability.The current systems analysis technique provides a comprehensive and objective method for assessing current systems.<br><a href="https://www.projectmanagement.com/process/popup.cfm?ID=23401">https://www.projectmanagement.com/process/popup.cfm?ID=23401</a><br><br><strong>2.Analysis of system's user need<br></strong>-User need's analysis as a valuable tool to enhance user satisfaction.  User Needs Analysis is part of the process of developing a site that will successfully meet the needs of prospective users. In addition to identifying the key needs, it can help balance potential conflicts in the desires of the site owners, stakeholders and target audience groups.  As well as identifying and prioritising the site goals of visitors, User Needs Analysis will help determine the technological requirements necessary for them to achieve those goals. <br><a href="http://usability.com.au/research/needs-analysis/">http://usability.com.au/research/needs-analysis/</a><br><br><strong>3.Information Gathering technique</strong><br>- The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:<br><br></div><ul><li><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.</li><li><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.</li><li><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.</li><li><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks. </li></ul><div><a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a></div><div><br>4<strong>. System's Analysis Report<br>-</strong>  The system analysis report is intended for all the project's major stakeholders: the client, the academic supervisors and the development team.<strong> <br>Firstly, </strong>this report will highlight the system vision by expanding on the project description, system capabilities and business benefits. The purpose of this initial section is to ensure that all stakeholders involved agree on the expectations and benefits of the system.  <br><br></div><div><strong>Secondly</strong>, in this deliverable the system requirements section is used to describe the functionality listed in the system vision and with the use of diagrams allow for all stakeholders to agree on the system requirements. With the use of a functional decomposition diagram the major subsystem for the Click &amp; Connect system have been described and all major functions identified. Alongside this a conceptual data model (entity relationship diagram) is presented to assist in explaining the main business processes and their relationships. It is expected that this diagram will change throughout the iterative development process. Following on, an architecture overview is utilized to highlight the current IT system and any proposed constraints. Finally, in the system requirements section a prioritized list of the system build plans has been included. The purpose of this section is to identify and describe the system requirements and constraints on the system.<br><br><strong>Thirdly</strong>, the project organisation section of this report focuses on the system development approach, the team structure, the overall project plan and risk management plan. Ultimately this section will describe how the system develop will be approached with both its iterative and incremental nature in each build. A Gantt chart has been included to list the major tasks that will be carried out and the proposed timetable that will be followed. This chart, as a part of the overall project plan, includes the tasks and activities highlighted in the system overview. Alongside this, the risk management plan outlines current risks and possible impact they would have on the project completion. The intention of this section is to ensure all stakeholders are across the incremental development and risks involved with this project.<br><br><strong>Finally,</strong> in this document a sign off sheet has been provided to ensure that the client has acknowledge the system overview report and to signal acceptance of the scope, content and expectations laid within. In this section if aspects are to be changed they need to be noted and agreed upon. As well an appendix has been included with client interactions and development artefacts.<br><br></div><div><a href="https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php">https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php</a><br><br>5<strong>.Accountant Role in System Analysis </strong></div><div> As analysts, accountants may perform certain types of analysis using financial data that is used to assist in making business decisions. From deciding which kinds of supplies to order, payment of bills to payroll, the accountant handles many intricate financial details on a daily basis. Advising on business operations can include issues, such as revenue and expenditure trends, financial commitments and future revenue expectations. The accountant also analyzes financial data to resolve certain discrepancies and irregularities that may arise. Recommendations may also involve developing efficient resources and procedures, while providing strategic recommendations for specific financial problems or situations. <br><a href="http://smallbusiness.chron.com/role-accountant-play-business-operations-411.html">http://smallbusiness.chron.com/role-accountant-play-business-operations-411.html</a><br><br><strong>System Design <br>1. User Interface Design <br></strong> User Interface (UI) Design focuses on anticipating what users might need to do and ensuring that the interface has elements that are easy to access, understand, and use to facilitate those actions. UI brings together concepts from <a href="https://www.usability.gov/what-and-why/interaction-design.html">interaction design</a>, <a href="https://www.usability.gov/what-and-why/visual-design.html">visual design</a>, and <a href="https://www.usability.gov/what-and-why/information-architecture.html">information architecture</a>. <br><br><a href="https://www.usability.gov/what-and-why/user-interface-design.html">https://www.usability.gov/what-and-why/user-interface-design.html</a><br><br><strong>2. Output Design </strong><br>Design outputs describe all of the ingredients that go into your device. These could include drawings, components, materials, parts, pieces, specifications, manufacturing instructions, and inspection procedures. <br><a href="https://www.greenlight.guru/blog/decoding-design-inputs-and-design-outputs">https://www.greenlight.guru/blog/decoding-design-inputs-and-design-outputs</a><br><br><strong>3. Input Design</strong><br>Design input is the starting point for product design. The requirements which form the design input establish a basis for performing subsequent design tasks and validating the design. Therefore, development of a solid foundation of requirements is the single most important design control activity.<strong><br></strong><a href="https://www.greenlight.guru/blog/decoding-design-inputs-and-design-outputs">https://www.greenlight.guru/blog/decoding-design-inputs-and-design-outputs</a><br> <br><strong>4. Security and Control Measure</strong><br>- The Security and Control Measures category encompasses the core activities directly related to protection and accounting of nuclear materials. It includes indicators of physical protection, control and accounting, insider threat prevention, security during transport, response capabilities, and a new cyber security indicator. <br><a href="http://ntiindex.org/indicators/security-and-control-measures/">http://ntiindex.org/indicators/security-and-control-measures/</a><br><br><strong>5.Accountant Role in Systems Designing</strong><br>- Accountants are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument. This function of designing AIS includes the design of managerial accounting information system to aid management in decision making processes.</div><div><br>Many accountants relinquished their traditional responsibilities to the new generation of computer professionals who were emerging in their organizations. Computer programmers, often with no accounting or business training, assumed full responsibility for the design of accounting information systems. As a result, many systems violated accounting principles and lacked necessary controls. Large system failures and computer frauds marked this period in accounting history. By the mid-1970s, in response to these problems, the accounting profession began to reassess the accountant’s professional and legal responsibilities for computer-based systems.</div><div><br>The design of the conceptual system involves specifying the criteria for identifying delinquent customers and the information that needs to be reported. The accountant determines the nature of the information required, its sources, its destination, and the accounting rules that need to be applied. The physical system is the medium and method for capturing and presenting the information. The computer professionals determine the most economical and effective technology for accomplishing the task. Hence, systems design should be a collaborative effort. Because of the uniqueness of each system and the susceptibility of systems to serious error and even fraud, the accountant’s involvement in systems design should be pervasive.</div><div><br><a href="http://bepls.com/beplsoctober2015/19.pdf">http://bepls.com/beplsoctober2015/19.pdf</a> </div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 06:39:44 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248380446</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248381175</link>
         <description><![CDATA[Analysis of system's user needs]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 06:42:22 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248381175</guid>
      </item>
      <item>
         <title>LAU POH LENG BB15110320</title>
         <author>pohleng0608</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248381994</link>
         <description><![CDATA[<div>&nbsp;</div><div><strong>System Analysis<br>1. Analysis of current system achievement</strong><br>Most systems are not developed from scratch. Usually, some form of information system and related procedures are currently in place. The analyst often begins the analysis by determining what elements, if any, of the current system should be preserved as part of the new system. This involves a rather detailed system survey. Facts pertaining to preliminary questions about the system are gathered and analyzed. As the analyst obtains a greater depth of understanding of the problem, he or she develops more specific questions for which more facts must be gathered. This process may go on through several iterations. When all the relevant facts have been gathered and analyzed, the analyst arrives at an assessment of the current system. Surveying the current system has both disadvantages and advantages. <br><em>Advantages of Surveying the Current System </em><br>-&nbsp; identify what aspects of the old system should be kept. Some elements of the system may be functionally sound and can provide the foundation for the new system. By fully understanding the current system, the analyst can identify those aspects worth preserving or modifying for use in the new system <br>-&nbsp; by surveying the current system, the analyst may determine conclusively the cause of the reported problem symptoms. Perhaps the root problem is not the information system at all; it may be a management or employee problem that can be resolved without redesigning the information system. We may not be able to identify the root cause of the problem if we discard the existing system without any investigation into the symptoms.<br><em>&nbsp;Disadvantages of Surveying the Current System </em>&nbsp;<br>-&nbsp; current system surveys stifle new ideas. By studying and modeling the old system, the analyst may develop a constrained notion about how the new system should function. The result is an improved old system rather than a radically new approach. An example is the implementation of an ERP system. The task of reviewing current organizational procedures may serve no purpose because the successful implementation of an ERP depends on reengineering these processes to employ the best business practices of the industry <br><a href="https://nscpolteksby.ac.id/ebook/files/Ebook/Accounting/Accounting%20Information%20System-James%20A.Hall%206%20(2008)/16.%20Part%204%20Chapter%2013%20-%20Managing%20the%20Systems%20Development%20Life%20Cycle.pdf">https://nscpolteksby.ac.id/ebook/files/Ebook/Accounting/Accounting%20Information%20System-James%20A.Hall%206%20(2008)/16.%20Part%204%20Chapter%2013%20-%20Managing%20the%20Systems%20Development%20Life%20Cycle.pdf</a> <br><br><strong>2. Analysis of a system’s user needs<br></strong>The aim&nbsp; is to provide a clear understanding of requirements as an early input to development projects. We help focus design work on those issues that are central to the success of a product or system in the eyes of the end-users. <br><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a></div><div><br></div><div><strong>3. Information gathering techniques</strong><br> 1. <em>Observation</em>. Observation involves passively watching the physical procedures of the system. This allows the analyst to determine what gets done, who performs the task, when they do it, how they do it, why they do it, and how long it takes. <br>2.&nbsp; <em>Task Participation.</em> Participation is an extension of observation, whereby the analyst takes an active role in performing the user’s work. This allows the analyst to experience firsthand the problems involved in the operation of the current system. For example, the analyst may work on the sales desk taking orders from customers and preparing sales orders. The analyst can determine that documents are improperly designed, that insufficient time exists to perform the required procedures, or that peak-load problems cause bottlenecks and processing errors. With hands-on experience, the analyst can often envision better ways to perform the task. <br> 3. <em>Personal Interviews. </em>Interviewing is a method of extracting facts about the current system and user perceptions about the requirements for the new system. The instruments used to gather these facts may be open-ended questions or formal questionnaires. <br>4. <em>&nbsp;Reviewing Key Documents.</em> The organization’s documents are another source of facts about the system being surveyed <br><a href="https://nscpolteksby.ac.id/ebook/files/Ebook/Accounting/Accounting%20Information%20System-James%20A.Hall%206%20(2008)/16.%20Part%204%20Chapter%2013%20-%20Managing%20the%20Systems%20Development%20Life%20Cycle.pdf">https://nscpolteksby.ac.id/ebook/files/Ebook/Accounting/Accounting%20Information%20System-James%20A.Hall%206%20(2008)/16.%20Part%204%20Chapter%2013%20-%20Managing%20the%20Systems%20Development%20Life%20Cycle.pdf</a> <br><br><strong>4.</strong> <strong>System’s analysis report<br>- </strong>summarizes and documents the findings of analysis activities and serves as a repository of data from which system designers can draw<br><a href="https://quizlet.com/4736934/ais-ch18-intro-to-systems-developmentanalysis-flash-cards/">https://quizlet.com/4736934/ais-ch18-intro-to-systems-developmentanalysis-flash-cards/</a><br> - This report presents management or the steering committee with the survey findings, the problems identified with the current system, the user’s&nbsp; needs, and the requirements of the new system.&nbsp; <br>- This document constitutes a formal contract that specifies the objectives and goals of the system. The systems analysis report should establish in clear terms the data sources, users, data files, general processes, data flows, controls, and transaction volume capacity. <br>-&nbsp; The systems analysis report does not specify the detailed design of the proposed system. For example, it does not specify processing methods, storage media, record structures, and other details needed to design the physical system. Rather, the report remains at the objectives level to avoid placing artificial constraints on the conceptual design phase. <br><a href="https://nscpolteksby.ac.id/ebook/files/Ebook/Accounting/Accounting%20Information%20System-James%20A.Hall%206%20(2008)/16.%20Part%204%20Chapter%2013%20-%20Managing%20the%20Systems%20Development%20Life%20Cycle.pdf">https://nscpolteksby.ac.id/ebook/files/Ebook/Accounting/Accounting%20Information%20System-James%20A.Hall%206%20(2008)/16.%20Part%204%20Chapter%2013%20-%20Managing%20the%20Systems%20Development%20Life%20Cycle.pdf</a> <br><br><strong>5.</strong> <strong>Accountant role in systems analysis</strong>&nbsp;</div><div>&nbsp;-Accountants are involved in the SDLC since information systems represent a&nbsp; significant financial transaction that consumes both financial and human resources.&nbsp;</div><div>The accountants are concerned with these projects since they have significant&nbsp; financial resource implications. Also, accountants are concerned with the quality of&nbsp;</div><div>the accounting information systems since these systems produce the information that&nbsp;</div><div>is reported to internal and external entities. Accountants may be called upon for input&nbsp; into non AIS applications if the application uses accounting data. The accountants&nbsp;</div><div>need to assess if any control threats exist<br><a href="https://www.coursehero.com/file/p3dmqhn/3-What-is-the-role-of-the-accountant-in-the-SDLC-Why-might-the-accountants-be/">https://www.coursehero.com/file/p3dmqhn/3-What-is-the-role-of-the-accountant-in-the-SDLC-Why-might-the-accountants-be/</a></div><div><strong><br>System Design <br>1. User interface design<br></strong>&nbsp;Designing the User Interface involves the following steps:</div><ul><li>Identify the Related Users - identify the characteristics of the (Human) users that will interact with the system to perform the requirements being considered in the current iteration. Focus on describing the primary users since the major part of the interactions involves these users.</li><li>Identify the Primary User Interface Elements - identify the primary windows of the system's user interface. Primary windows are those windows that the user will interact with the most (those user-interface elements that are central to the user's mental model of the system).</li><li>Define the <a href="https://www.fsa.usda.gov/Assets/USDA-FSA-Public/usdafiles/SDLC-non-secure/Development-Process-/High-Level-Design/Design-System-Interface/Docs/sdlc_template_nav_map.doc"><strong>Navigation Map</strong></a> - the Navigation Map defines what the valid navigation paths through the user-interface elements are for the user to perform system features. It does not need to contain all of the possible paths through the user-interface elements. The goal is for it to serve as a road map of the system's user interface.&nbsp;</li></ul><div>user interface design, such as form design, menu layout, choice of colors, icon design, and&nbsp;</div><div>screen layout of display interfaces<br>&nbsp;<a href="https://www.researchgate.net/publication/220892325_Integrating_Human-Computer_Interaction_Development_into_SDLC_A_Methodology">https://www.researchgate.net/publication/220892325_Integrating_Human-Computer_Interaction_Development_into_SDLC_A_Methodology</a></div><div><strong><br>2. Output design<br></strong>The objective of output design is to determine the nature, format, content, and timing of printed report, document and screen display. It require cooperation between users and designers.<br><a href="https://www.slideshare.net/sharingslide4u/ais-romney-2006-slides-20-system-design">https://www.slideshare.net/sharingslide4u/ais-romney-2006-slides-20-system-design</a><br> <strong><br>3. Input design</strong></div><div>When evaluating <em>input design, </em>the design team must identify the different types of data input and optimal input method. The two principal types of data input are forms and computer screen.&nbsp;</div><div>&nbsp;&nbsp;</div><div><strong>4. Security and control measures<br></strong>The control design include validation, accuracy, numerical control, maintainability, audit control, authorization, security,availability, intergrity.<br>https://www.usfsp.edu/gkearns/ACG6936/ppt/ch04.ppt<br><strong><br>5. Accountant role in system design<br>- </strong>play an active role in designing system controls&nbsp;<br><br>https://www.usfsp.edu/gkearns/ACG6936/ppt/ch04.ppt<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 06:45:22 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248381994</guid>
      </item>
      <item>
         <title>MAZWAN BIN SARIHASAN (BB15110382)</title>
         <author>Mazwan</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248400538</link>
         <description><![CDATA[<div><strong>System Analysis<br></strong><mark>1)</mark><strong><mark> </mark></strong><mark>Analysis of current system achievement</mark><br>The systems analyst needs to know the details of current system functions: the who (the people who are involved), what (the business activity), where (the environment in which the work takes place), when (the timing), and how (how the current procedures are performed) of the business under study. The analyst must then ask why the business uses the current system. There may be good reasons for doing business using the current methods, and these should be considered when designing any new system.<br> <br><mark>2) Analysis of a system’s user needs</mark><br>The developer of the system must concern about the user's needs .This is due:</div><ul><li>Poorly specified user requirements are one of the most significant factors behind IT project failure.</li><li>A successful product or system requires a proper understanding of both user and organisational requirements - we help integrate and balance the two in the specification process.</li><li>Avoid over-reliance on internally generated requirements (what its believed that users want), as opposed to data from end-user requirements studies (what users actually need).</li><li>Usability Partners support development projects, bringing key user data into the design process and analysing user needs, their work practice, and the situations in which they work.</li></ul><div><br><mark>3) Information gathering techniques</mark><br>There's few technique to gather information that is :</div><ul><li><em>Surveys</em> –&nbsp; conducted electronically or on paper.</li><li><em>Interviews</em> – conducted face-to-face.</li><li>&nbsp;<em>Evaluation of an existing product</em> – provides a range of useful information (even competitor products can be tested)&nbsp;</li><li><em>Task analysis</em> – a deeper analysis of users work with a system, useful for analysing how user's work tasks should be supported by functionality in a system.&nbsp;</li></ul><div><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a></div><div><br><mark>4) System’s analysis report</mark></div><div>A formal systems analysis report, prepared and presented to the steering committee, contains:</div><div>–reasons for system analysis</div><div>–scope of study</div><div>–problem identified with current system</div><div>–statement of user requirements</div><div>–resource implications</div><div>–recommendations</div><div><a href="http://www.cengage.com/resource_uploads/downloads/1439078572_248443.pptx">www.cengage.com/resource_uploads/downloads/1439078572_248443.pptx</a>&nbsp;</div><div><br><mark>5) Accountant role in systems analysis</mark></div><div>First is as an a user.&nbsp; accountants must provide a clear picture of their problems and needs to the systems professional. <br>Second as an auditor.&nbsp; Accountant will help to require special features that must be designed into the system. <br><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc</a><br><br>&nbsp;</div><div><strong>System Design <br><br></strong><mark>1. User interface design<br></mark>&nbsp;User interface design is the design of user interfaces for software or machines, such as the look of a mobile app, with a focus on <em>ease of use</em> and <em>pleasurability</em> for the user. It is usually refers to the design of graphical user interfaces—but can also refer to others, such as natural and voice user interfaces. In other words, user interface design is a display featured of the system<br><a href="https://www.interaction-design.org/literature/topics/ui-design">https://www.interaction-design.org/literature/topics/ui-design</a> <br><mark><br>2. Output design<br></mark>The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts. <br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br><mark>3. Input design</mark><strong><br></strong>In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc. <strong><br><br></strong><mark>4. Security and control measures</mark><br><strong>System security</strong> refers to protecting the system from theft, unauthorized access and modifications, and accidental or unintentional damage. In computerized systems, security involves protecting all the parts of computer system which includes data, software, and hardware. Systems security includes system privacy and system integrity.</div><ul><li><strong>System privacy</strong> deals with protecting individuals systems from being accessed and used without the permission/knowledge of the concerned individuals.</li><li><strong>System integrity</strong> is concerned with the quality and reliability of raw as well as processed data in the system.</li></ul><div><strong>Control Measures<br></strong>a)<strong> </strong>Backup<br>b) Physical Access Control to Facilities<br>c) Using Logical or Software Control<br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm</a></div><div><br><mark>5. Accountant role in systems designing<br></mark>Accountants are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument. This function of designing AIS includes the design of managerial accounting information system to aid management in decision making processes.&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 08:09:24 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248400538</guid>
      </item>
      <item>
         <title>NADIATUL REHAN BINTI ABDULLADIN (BB15110440)</title>
         <author>nadiatulrehan</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248406782</link>
         <description><![CDATA[]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/251531483/c62c533c0a0f7363fd25e6600d54ec5c/SYSTEM_ANALYSIS_and_DESIGN.docx" />
         <pubDate>2018-04-04 08:39:20 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248406782</guid>
      </item>
      <item>
         <title>NURULIZATTI BINTI HALIM (BB14110555)</title>
         <author>nurulizatti95</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248410874</link>
         <description><![CDATA[]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/196625553/4900b6e5049d192b3b9f0849c48990f1/SYSTEM_DESIGN___ANALYSIS.docx" />
         <pubDate>2018-04-04 08:58:21 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248410874</guid>
      </item>
      <item>
         <title>SHARMILADEVI ARUMUGAM (BB15110667)</title>
         <author>sharmila25</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248413001</link>
         <description><![CDATA[<div>A) <strong>SYSTEM ANALYSIS</strong><br><br><mark>1) Analysis of current system achievement</mark><br><br>The system analyst needs to know the details of current system functions: the who (the people who are involved), what(the business activity), where(the environment in which the work takes place), when (the timing), and how(how the current procedures are performed) of the business under study. The analyst must ask why the business uses the current system. There may be good reasons for doing business using the current methods, and these should be considered when designing any new system.<br><br><mark>2. Analysis of a system's user needs.</mark><br><br>Typical requirements gathering and analysis methods include:<br>a)Surveys – both open-ended and focused surveys, conducted electronically or on paper.<br>(b) Interviews – typically conducted face-to-face, but also over the telephone if deemed more appropriate.<br>c) Focus groups – whilst being poorly suited to evaluating a product, focus groups are useful for discussing possible user requirements and brainstorming ideas.<br>d) Field studies – observing the end-user situation and the environment in which a new product or system will be used is often extremely useful in understanding user needs.<br>e) Evaluation of an existing product – provides a range of useful information (even competitor products can be tested). Usability evaluation reveals and clarifies good and bad aspects of current solutions - valuable input to new design work.<br>f) Task analysis – a deeper analysis of users work with a system, useful for analysing how user's work tasks should be supported by functionality in a system.<br>g) User personas and usage scenarios – concrete and illustrative data about typical users, their characteristics, usage situation, tasks and goals. Particularly useful in supporting early user interface design work.<br>h) Formulation of usability goal and overall design criteria – help focus and steer the design process, supporting the evaluation of early concepts, prototypes and final designs.<br><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a><br><br><mark>3. Information gathering techiques</mark><br> <br>Managing information involves gathering and distributing necessary information and assimilating them on the project management activities and processes. The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:<br><br></div><ul><li><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.</li><li><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.</li><li><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.</li><li><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks. </li></ul><div><a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a><br><br><mark>4.System's analysis report</mark><br><br>The purpose of this report is to present the proposed system analysis for the client, Click &amp; Connect, with the intention of ensuring all stakeholders involved agree on the planned solution. Throughout the project the analysis, development, implementation and testing phases will be conducted using, the industry standard, agile development life cycle. This specifies that changes can be made if required and appropriate. The system analysis report is intended for all the project's major stakeholders: the client, the academic supervisors and the development team.<br><a href="https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php">https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php</a><br><br><mark>5. Accountant role in systems analysis.<br></mark> </div><div>Accountants are involved in the SDLC since information systems represent a significant financial transaction that consumes both financial and human resources. </div><div>The accountants are concerned with these projects since they have significant financial resource implications. Also, accountants are concerned with the quality of the accounting information systems since these systems produce the information that is reported to internal and external entities. Accountants may be called upon for input into non AIS applications if the application uses accounting data. The accountants need to assess if any control threats exist <br><a href="https://www.coursehero.com/file/p3dmqhn/3-What-is-the-role-of-the-accountant-in-the-SDLC-Why-might-the-accountants-be/">https://www.coursehero.com/file/p3dmqhn/3-What-is-the-role-of-the-accountant-in-the-SDLC-Why-might-the-accountants-be/</a><br><br>B) <strong>SYSTEM DESIGN</strong><br><br><mark>1. User interface design</mark><br> <br>User Interface Design is the design of websites, computers, appliances, machines, mobile communication devices, and software applications with the focus on the user’s experience and interaction. The goal of user interface design is to make the user’s interaction as simple and efficient as possible, in terms of accomplishing user goals—what is often called user-centered design. <br><a href="https://www.freshtilledsoil.com/what-is-user-interface-design/">https://www.freshtilledsoil.com/what-is-user-interface-design/</a><br><br><mark>2.Output design</mark><em><br><br></em> The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.  </div><div>The objectives of input design are :<br>a)to develop output design that serves the intended purpose and eliminates the production of unwanted output.<br>b)To develop the output design that meets the end users requirements.<br>c)To deliver the appropriate quantity of output.<br>d)To form the output in appropriate format and direct it to the right person.<br>e)To make the output available on time for making good decisions. <br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br><mark>3. Input design</mark><br> <br>In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.<br>Therefore, the quality of system input determines the quality of system output. Welldesigned input forms and screens have following properties −<br>a)It should serve specific purpose effectively such as storing, recording, and retrieving the information.<br>b)It ensures proper completion with accuracy.<br>c)It should be easy to fill and straightforward.<br>d)It should focus on user’s attention, consistency, and simplicity. <br> </div><div>The objectives of input design are :<br>a)To design data entry and input procedures<br>b)To reduce input volume<br>c)To design source documents for data capture or devise other data capture methods<br>d)To design input data records, data entry screens, user interface screens, etc.<br>e)To use validation checks and develop effective input controls. <br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br><mark>4. Security and control measures</mark><br><br> System security refers to protecting the system from theft, unauthorized access and modifications, and accidental or unintentional damage. In computerized systems, security involves protecting all the parts of computer system which includes data, software, and hardware. Systems security includes system privacy and system integrity.<br><br>a) <strong>System privacy</strong> deals with protecting individuals systems from being accessed and used without the permission/knowledge of the concerned individuals.<br> <br>b)<strong>System integrity</strong> is concerned with the quality and reliability of raw as well as processed data in the system.<br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm</a><br><br>5. Accountant role in Systems Design<br><br> Accountants are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument. This function of designing AIS includes the design of managerial accounting information system to aid management in decision making processes. An appreciation of the accountant’s responsibility for system design requires a historic perspective that predates the computer as a business information tool. Traditionally, accountants have been responsible for key aspects of the information system, including assessing the information needs of users, defining the content and format of output reports, specifying sources of data, selecting the appropriate accounting rules, and determining the controls necessary to preserve the integrity and efficiency of the information system.<br> <a href="http://bepls.com/beplsoctober2015/19.pdf">http://bepls.com/beplsoctober2015/19.pdf</a><br><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 09:07:31 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248413001</guid>
      </item>
      <item>
         <title>VERONECA DUMIEH (BB15110759)</title>
         <author>veroneca96</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248413728</link>
         <description><![CDATA[<div><strong>System Analysis</strong></div><ol><li>Analysis of current system achievement</li></ol><div> The systems analyst needs to know the details of current system functions: the who (the people who are involved), what (the business activity), where (the environment in which the work takes place), when (the timing), and how (how the current procedures are performed) of the business under study. The analyst must then ask why the business uses the current system. There may be good reasons for doing business using the current methods, and these should be considered when designing any new system.<br> <br><a href="http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/">http://www.w3computing.com/systemsanalysis/identifying-problems-opportunities-objectives-sdlc/</a> <br>2. Analysis of a system’s user needs <br>    The developer of the system must concern about the user's needs .This is due:<br>-Poorly specified user requirements are one of the most significant factors behind IT project failure.<br>-A successful product or system requires a proper understanding of both user and organisational requirements - we help integrate and balance the two in the specification process.<br>-Avoid over-reliance on internally generated requirements (what its believed that users want), as opposed to data from end-user requirements studies (what users actually need).<br>-Usability Partners support development projects, bringing key user data into the design process and analyzing user needs, their work practice, and the situations in which they work. </div><div><br>3.Information gathering techniques</div><div> </div><div>There's few technique to gather information that is :</div><ul><li><em>Surveys</em> –  conducted electronically or on paper.</li><li><em>Interviews</em> – conducted face-to-face.</li><li> <em>Evaluation of an existing product</em> – provides a range of useful information (even competitor products can be tested) </li><li><em>Task analysis</em> – a deeper analysis of users work with a system, useful for analysing how user's work tasks should be supported by functionality in a system. </li></ul><div><a href="http://www.usabilitypartners.se/services/user-requirements-analysis.php">http://www.usabilitypartners.se/services/user-requirements-analysis.php</a> <br><br>4.System’s analysis report<br><br><em>The purpose of this report is to present the proposed system analysis for the client with the intention of ensuring all stakeholders involved agree on the planned solution. Throughout the project the analysis, development, implementation and testing phases will be conducted using, the industry standard, agile development life cycle. This specifies that changes can be made if required and appropriate. The system analysis report is intended for all the project's major stakeholders: the client, the academic supervisors and the development team.<br>(</em><a href="https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php"><em>https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php</em></a><em>)</em><br><br>5.Accountant role in systems analysis<br><br> -Accountants are involved in the SDLC since information systems represent a  significant financial transaction that consumes both financial and human resources. </div><div>The accountants are concerned with these projects since they have significant  financial resource implications. Also, accountants are concerned with the quality of </div><div>the accounting information systems since these systems produce the information that </div><div>is reported to internal and external entities. Accountants may be called upon for input  into non AIS applications if the application uses accounting data. The accountants </div><div>need to assess if any control threats exist<br><a href="https://www.coursehero.com/file/p3dmqhn/3-What-is-the-role-of-the-accountant-in-the-SDLC-Why-might-the-accountants-be/">https://www.coursehero.com/file/p3dmqhn/3-What-is-the-role-of-the-accountant-in-the-SDLC-Why-might-the-accountants-be/</a> </div><div> </div><div><strong>System Design <br></strong><br></div><ol><li> User interface design</li></ol><div>          </div><div>- User Interface Design is the design of websites, computers, appliances, machines, mobile communication devices, and software applications with the focus on the user’s experience and interaction. The goal of user interface design is to make the user’s interaction as simple and efficient as possible, in terms of accomplishing user goals—what is often called user-centered design.<br><a href="https://www.freshtilledsoil.com/what-is-user-interface-design/">https://www.freshtilledsoil.com/what-is-user-interface-design/</a><br><br>2. Output design<br>-  The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.</div><div>The objectives of input design are−</div><ul><li>To develop output design that serves the intended purpose and eliminates the production of unwanted output.</li><li>To develop the output design that meets the end users requirements.</li><li>To deliver the appropriate quantity of output.</li><li>To form the output in appropriate format and direct it to the right person.</li><li>To make the output available on time for making good decisions. </li></ul><div> </div><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm </a></div><div><br>3. Security and control measures<br><strong>System security</strong> refers to protecting the system from theft, unauthorized access and modifications, and accidental or unintentional damage. In computerized systems, security involves protecting all the parts of computer system which includes data, software, and hardware. Systems security includes system privacy and system integrity.</div><ul><li><strong>System privacy</strong> deals with protecting individuals systems from being accessed and used without the permission/knowledge of the concerned individuals.</li><li><strong>System integrity</strong> is concerned with the quality and reliability of raw as well as processed data in the system.</li></ul><div><strong>Control Measures<br></strong>a)<strong> </strong>Backup<br>b) Physical Access Control to Facilities<br>c) Using Logical or Software Control<br><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm</a></div><div><br> 4. Accountant role in systems designing <br> </div><div>Accountants are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument. This function of designing AIS includes the design of managerial accounting information system to aid management in decision making processes.</div><div><br>Many accountants relinquished their traditional responsibilities to the new generation of computer professionals who were emerging in their organizations. Computer programmers, often with no accounting or business training, assumed full responsibility for the design of accounting information systems. As a result, many systems violated accounting principles and lacked necessary controls. Large system failures and computer frauds marked this period in accounting history. By the mid-1970s, in response to these problems, the accounting profession began to reassess the accountant’s professional and legal responsibilities for computer-based systems.</div><div><br>The design of the conceptual system involves specifying the criteria for identifying delinquent customers and the information that needs to be reported. The accountant determines the nature of the information required, its sources, its destination, and the accounting rules that need to be applied. The physical system is the medium and method for capturing and presenting the information. The computer professionals determine the most economical and effective technology for accomplishing the task. Hence, systems design should be a collaborative effort. Because of the uniqueness of each system and the susceptibility of systems to serious error and even fraud, the accountant’s involvement in systems design should be pervasive.</div><div><br><a href="http://bepls.com/beplsoctober2015/19.pdf">http://bepls.com/beplsoctober2015/19.pdf</a> </div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 09:10:08 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248413728</guid>
      </item>
      <item>
         <title>Narliza binti Lesar (</title>
         <author>NarlizaLesar</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248415735</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 09:18:20 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248415735</guid>
      </item>
      <item>
         <title>Narliza binti Lesar (BB15110442)</title>
         <author>NarlizaLesar</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248415740</link>
         <description><![CDATA[]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/200826281/b1cc1d34a0cb7adbecb697cddb9ef8e8/Lecture_5_padlet_analysis_and_design.docx" />
         <pubDate>2018-04-04 09:18:22 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248415740</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248422716</link>
         <description><![CDATA[ccountant role in systems analysis .]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 09:52:24 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248422716</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248422730</link>
         <description><![CDATA[ccountant role in systems analysis .]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 09:52:27 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248422730</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248424977</link>
         <description><![CDATA[]]></description>
         <enclosure url="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/" />
         <pubDate>2018-04-04 10:03:36 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248424977</guid>
      </item>
      <item>
         <title>IFZAATUL AZRHA BINTI ABD LATIF (BB15161020)</title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248426391</link>
         <description><![CDATA[<div>&nbsp;</div><div><strong>System Analysis</strong> <br><strong>1.</strong> <strong>Analysis of current system achievement</strong></div><div>System analysis is the process of observing systems for troubleshooting or development purposes. It is applied to information technology where computer based systems required defined analysis according to their design. <a href="https://www.techopedia.com/definition/9611/systems-analysis">https://www.techopedia.com/definition/9611/systems-analysis</a> <br><br><strong>2.</strong> <strong>Analysis of a system’s user needs</strong></div><div>This is refer to the user’s needs from the system. This describe what the user does with the system such as what activities that users must be able to perform. User requirements are generally documented in a User Requirements Document (URD) using narrative text. <a href="http://enfocussolutions.com/business-user-and-system-requirements/">http://enfocussolutions.com/business-user-and-system-requirements/</a> <br><br><strong>3. Information gathering techniques</strong></div><div>There’s a few technique to gather information :&nbsp;<br><br></div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<strong><em>One-on-one interviews&nbsp;</em></strong></div><div>This is the most common technique for gathering requirements is to sit down with the clients and ask them what they need.&nbsp;</div><div>&nbsp;</div><div>·&nbsp; &nbsp; &nbsp; &nbsp; <strong><em>&nbsp;Group interviews</em></strong>&nbsp;</div><div>This similar to one-on-one interview, except that more than one person is being interviewed and usually two to four.&nbsp;</div><div>&nbsp;</div><div>·&nbsp; &nbsp; &nbsp; &nbsp;<strong><em>&nbsp; Questionnaires&nbsp;</em></strong></div><div>Much more informal and they are good tools to gather requirements from stakeholders in remote locations or those who will have only minor input into the overall requirements.&nbsp;</div><div>&nbsp;</div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<strong><em>Prototyping&nbsp;</em></strong></div><div>This is a relatively modern technique for gathering requirements. In this approach we gather preliminary requirements that you use to build an initial version of the solution.&nbsp;</div><div>&nbsp;</div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<strong><em>Use cases</em></strong>&nbsp;</div><div>Use cases are basically stories that describe how discrete processes work. The stories include people and describe how the solution works from a user perspective.&nbsp;</div><div>&nbsp;</div><div>·&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<strong><em>Brainstorming&nbsp;</em></strong></div><div>This is the solution for brand new and needs to be created as a set of ideas that people can agree to. <br><br><strong>4. System’s analysis report</strong></div><div>This is a formal report that prepared and presented to the steering committee. The report have a content such as the reasons for system analysis, the scope of study, the problem identified with current system, the statement of user requirements, the resource implications, and the recommendations. <br><br><strong>5. Accountant role in systems analysis&nbsp;</strong></div><div>An accountant was participate in systems development as members of the development team. Their involvement often extends beyond the development of strictly accounting information systems applications. <a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc</a></div><div><br></div><div><strong>System Design <br></strong><br><strong>1. User interface design</strong></div><div>This is the design of user interfaces for software or machines, such as the look of mobile app, with a focus on ease of use and pleasurability for the user. This usually refers to the design of graphical user interfaces and also can be refer to others such as natural and voice user interfaces. <br><br><strong>2. Output design</strong></div><div>The output design is the most important task of any system. During output design, developers identify the type of outputs needed and consider the necessary output controls and prototype report layouts. <a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a> <br><br><strong>3. Input design</strong></div><div>In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc. <a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a> <br><br><strong>4. Security and control measures&nbsp;</strong></div><div>The security and control measures category encompasses the core activities directly related to protection and accounting of nuclear materials. It includes indicators of physical protection, control and accounting, insider threat prevention, security during transport, response capabilities, and a new cybersecurity indicator. <a href="http://ntiindex.org/indicators/security-and-control-measures/">http://ntiindex.org/indicators/security-and-control-measures/</a> <br><br><strong>5. Accountant role in systems designing</strong></div><div>Accountant plays an important role in the conceptual design of the system. They must recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood. <a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/</a> &nbsp;<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 10:11:47 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248426391</guid>
      </item>
      <item>
         <title>JANANI VENGU </title>
         <author>janani_vengu</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248433845</link>
         <description><![CDATA[<div>(BB15110266)<br>System Anal<br><br>1. Analysis of current system achievement<br><br></div><div>Systems Analysis<br><br></div><div>It is a process of collecting and interpreting facts, identifying the problems, and<br><br></div><div>decomposition of a system into its components.<br><br></div><div>System analysis is conducted for the purpose of studying a system or its parts in order to<br><br></div><div>identify its objectives. It is a problem solving technique that improves the system and<br><br></div><div>ensures that all the components of the system work efficiently to accomplish their purpose.<br><br></div><div>Systems Design<br><br></div><div>It is a process of planning a new business system or replacing an existing system by<br><br></div><div>defining its components or modules to satisfy the specific requirements. Before planning,<br><br></div><div>you need to understand the old system thoroughly and determine how computers can best<br><br></div><div>be used in order to operate efficiently.<br><br></div><div>System Design focuses on how to accomplish the objective of the system.<br><br></div><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_tutorial.pdf<br></a><br></div><div>2. Analysis of system user needs<br><br></div><div>• Identifying needs:<br><br></div><div>– Understand as much as possible about the users, as well as their work and the context of their<br><br></div><div>    Work.<br><br></div><div>– System under development should support users in achieving their goals<br><br></div><div><a href="https://www.ics.uci.edu/~kobsa/courses/INF231/07F/Ch_7_Presentation.pdf">https://www.ics.uci.edu/~kobsa/courses/INF231/07F/Ch_7_Presentation.pdf<br></a><br></div><div>3. . The information gathering technique<br><br></div><div>The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:<br><br></div><div>Brainstorming: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.<br><br></div><div>Delphi technique: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.<br><br></div><div>Root cause analysis: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.<br><br></div><div>Interviewing: Stakeholders, participants, and experts are interviewed to identify risks.<br><br></div><div><a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/<br></a><br></div><div>4.System analysis report<br><br></div><div>The System Analysis Report also includes the System Health Score(1) which indicates the health<br><br></div><div>of the system based upon a comparison of specific criteria relative to other systems subscribed to<br><br></div><div>Guardian Support on a global basis. The System Health Score included in this report is based on<br><br></div><div>the status of the system at the end of this reporting period. Scores are recorded on a weekly<br><br></div><div>basis, and the highest score of the month is included in the trend.<br><br></div><div><a href="http://www.emerson.com/documents/automation/guardian-sample-system-analysis-report-en-67944.pdf">http://www.emerson.com/documents/automation/guardian-sample-system-analysis-report-en-67944.pdf<br></a><br></div><div>5. Accountant role in systems analysis<br><br></div><div>Accountants are involved in systems development in three ways. First, accountants are users. Second, accountants participate in systems development as members of the development team. Third, accountants are involved in systems development as auditors.<br><br></div><div><a href="http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/">http://www.engineering-bachelors-degree.com/business-information-management/uncategorized/managing-the-systems-development-life-cyclethe-accountants-role-in-managing-the-sdlc/<br></a><br></div><div> System design</div><div> </div><div>1.User interface design<br><br></div><div>User interface (UI) design is the design of user interfaces for software or machines, such as the look of a mobile app, with a focus on ease of use and pleasurability for the user. UI design usually refers to the design of graphical user interfaces—but can also refer to others, such as natural and voice user interfaces.<br><br></div><div><a href="https://www.interaction-design.org/literature/topics/ui-design">https://www.interaction-design.org/literature/topics/ui-design<br></a><br></div><div>2.Output design<br><br></div><div> Design output to serve the intended purpose - essentially, this means that the systems objectives should be met but the objectives should be linked to the business tactics. Design output to fit the user - design for the person, not the position; remember human information processing differences; issue of detail versus summary.<br><br></div><div><a href="http://spot.colorado.edu/~kozar/Ch15.html">http://spot.colorado.edu/~kozar/Ch15.html<br></a><br></div><div>3.Input design<br><br></div><div>Input design the link between information system and the user. It comprises the developing specification and procedure for data preparation  and this steps are necessary to put transaction  data      in to a usable for form  processing can be achieved by inspecting the computer to read the data for written or printed docuent or it can occur by having people keying the data directly into the system.<br><br></div><div><a href="https://www.slideshare.net/madhukarreddy007/input-and-output-design">https://www.slideshare.net/madhukarreddy007/input-and-output-design<br></a><br></div><div>4. Security and control measures<br><br></div><div>System security refers to protecting the system from theft, unauthorized access and modifications, and accidental or unintentional damage. In computerized systems, security involves protecting all the parts of computer system which includes data, software, and hardware. Systems security includes system privacy and system integrity.System privacy deals with protecting individuals systems from being accessed and used without the permission/knowledge of the concerned individuals.System integrity is concerned with the quality and reliability of raw as well as processed data in the system.<br><br></div><div>There are variety of control measures which can be broadly classified as follows −<br><br></div><div>Backup<br><br></div><div>Regular backup of databases daily/weekly depending on the time criticality and size.Incremental back up at shorter intervals.Backup copies kept in safe remote location particularly necessary for disaster recovery.Duplicate systems run and all transactions mirrored if it is a very critical system and cannot tolerate any disruption before storing in disk.<br><br></div><div>https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_security_audit.htm<br><br></div><div> <br><br></div><div> <br><br></div><div>5. Accountant role in system designing<br><br></div><div>Accountant are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument .<br><br></div><div><a href="http://www.accountantnextdoor.com/accountants%E2%80%99-role-in-the-accounting-information-system/">http://www.accountantnextdoor.com/accountants%E2%80%99-role-in-the-accounting-information-system/<br></a><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 10:48:23 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248433845</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248440877</link>
         <description><![CDATA[User interface (UI) design is the design of user interfaces for software or machines, such as the look of a mobile app, with a focus on ease of use and pleasurability for the user. UI design usually refers to the design of graphical user interfaces—but can also refer to others, such as natural and voice user interfaces. 

https://www.interaction-design.org/literature/topics/ui-design]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 11:27:04 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248440877</guid>
      </item>
      <item>
         <title>ANUAR BIN SAMAD</title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248466427</link>
         <description><![CDATA[<div><strong>BB15110822</strong><br> <br><strong><mark>System Analysis</mark></strong></div><div><em>System analysis </em>is the process of gathering and interpreting facts, diagnosing problems, and using the information to recommend improvements to the system. This is the job of the systems analyst.<br><br>1.<strong>Analysis of current system &nbsp; achievement<br></strong>The systems analyst needs to know the details of current system functions: the who (the people who are involved), what (the business activity), where (the environment in which the work takes place), when (the timing), and how (how the current procedures are performed) of the business under study. The analyst must then ask why the business uses the current system. There may be good reasons for doing business using the current methods, and these should be considered when designing any new system.<strong><br><br>2.Analysis of a system’s user needs<br></strong>Understanding user requirements is an integral part of information systems design and is critical to the success of interactive systems. It is now widely understood that successful systems and products begin with an understanding of the needs and requirements of the users. As specified in the ISO 13407 standard (ISO, 1999), user-centred design begins with a thorough understanding of the needs and requirements of the users.&nbsp;<br><br></div><div><strong>3.Information gathering techniques</strong> <br>Managing information involves gathering and distributing necessary information and assimilating them on the project management activities and processes. The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows: <br><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.<br><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.<br><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.<br><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks.<br><br>4.<strong>System’s analysis report<br></strong>System’s analysis report is to present the proposed system analysis for the client with the intention of ensuring all stakeholders involved agree on the planned solution. Throughout the project the analysis, development, implementation and testing phases will be conducted using, the industry standard, agile development life cycle. This specifies that changes can be made if required and appropriate. The system analysis report is intended for all the project's major stakeholders: the client, the academic supervisors and the development team.<br><strong><br>5. Accountant role in systems analysis&nbsp;</strong></div><div>Accountants are involved in the SDLC since information systems represent a significant financial transaction that consumes both financial and human resources.&nbsp; The accountants are concernedwith these projects since they have significant financial resource implications. Also, accountants are concerned with the quality of the accounting information systems since these systems produce the information that is reported to internal and external entities. Accountants may be called upon for input into non AIS applications if the application uses accounting data. The accountants need to assess if any control threats exist.<br><br></div><div><strong><br></strong><strong><mark>&nbsp;System Design&nbsp;</mark></strong></div><div><em>System design </em>is the process of planning a new business system or one to replace or complement an existing system. But before this planning can be done, we must thoroughly understand the old system and determine how computers can best be used to make its operation more effective.&nbsp;</div><div><br>1.<strong>User interface design</strong></div><div>User interface (UI) design is the design of user interfaces for software or machines, such as the look of a mobile app, with a focus on <em>ease of use</em> and <em>pleasurability</em> for the user. UI design usually refers to the design of graphical user interfaces—but can also refer to others, such as natural and voice user interfaces.</div><div>Since software is intangible, the only way a user can control or interact with it is through a designed user interface. A well-designed user interface creates a user experience that the designer intended and/or a user experience that the user appreciates.&nbsp;</div><div>Many user interfaces are designed with a focus on <em>usability</em> and <em>efficiency</em>. Users should be able to achieve their goals as efficiently as possible, without focusing too much on the user interface itself. In that sense, a well-designed user interface becomes effectively <em>invisible</em> to those using it. In other words, they interact directly with the ‘reality’ the design portrays without reckoning on the point that, for example, thumbing button icons through the glass screens of their handheld devices is responsible for producing changes in what they see. However, usability and efficiency might not be the only measure of a well-designed user interface; a user interface might be designed to create a fun and pleasurable experience for users instead</div><div>https://www.interaction-design.org/literature/topics/ui-design</div><div><br>2<strong>.Output design</strong></div><div>Output is the outcome of processing. A quality output is one, which meets the requirements of the end user and presents the information clearly. In any system results of processing are communicated to the users and to other system through outputs. In output design it is determined how the information is to be displaced for immediate need and also the hard copy output. It is the most important and direct source information to the user. Efficient and intelligent output design improves the system’s relationship to help user decision-making. Designing computer output should proceed in an organized, well thought out manner; the right output must be developed while ensuring that each output element is designed so that people will find the system can use easily and effectively. When analysis design computer output, they should Identify the specific output that is needed to meet the requirements. Select methods for presenting information. Create document, report, or other formats that contain information produced by the system. The output form of an information system should accomplish one or more of the following objectives. Convey information about past activities, current status or projections of the Future. Signal important events, opportunities, problems, or warnings. Trigger an action. Confirm an action.<br><br>3<strong>. Input design</strong></div><div>Inputs are the elements (material, human resources, and information) that enter the system for processing. The input design is the link between the information system and the user. It comprises the developing specification and procedures for data preparation and those steps are necessary to put transaction data in to a usable form for processing can be achieved by inspecting the computer to read data from a written or printed document or it can occur by having people keying the data directly into the system. The design of input focuses on controlling the amount of input required, controlling the errors, avoiding delay, avoiding extra steps and keeping the process simple. The input is designed in such a way so that it provides security and ease of use with retaining the privacy. Input Design is the process of converting a user-oriented description of the input into a computer-based system. This design is important to avoid errors in the data input process and show the correct direction to the management for getting correct information from the computerized system. It is achieved by creating user-friendly screens for the data entry to handle large volume of data. The goal of designing input is to make data entry easier and to be free from errors. The data entry screen is designed in such a way that all the data manipulates can be performed. It also provides record viewing facilities. When the data is entered it will check for its validity. Data can be entered with the help of screens. Appropriate messages are provided as when needed so that the user will not be in maize of instant.&nbsp;</div><div><a href="https://www.slideshare.net/madhukarreddy007/input-and-output-design">https://www.slideshare.net/madhukarreddy007/input-and-output-design</a><br><br><strong>4. Security and control measures<br>Security controls</strong> are safeguards or <a href="https://en.wikipedia.org/wiki/Countermeasure_(computer)"><strong>countermeasures</strong></a> to avoid, detect, counteract, or minimize <a href="https://en.wikipedia.org/wiki/Security_risk"><strong>security</strong></a><strong> </strong><a href="https://en.wikipedia.org/wiki/Risks"><strong>risks</strong></a> to physical property, information, computer systems, or other assets. <br><strong><br>5. Accountant role in systems designing&nbsp;</strong></div><div>&nbsp;The accountant plays an important role in the conceptual design of the system. He or she must recognize control implications of each alternative design and ensure that accounting conventions and legal requirements are understood. These issues need not be specified in detail at this point, but they should be recognized as items to be addressed during the construct phase of the system. Furthermore, the auditability of a system depends in part on its design characteristics. Some computer auditing techniques require systems to be designed with built-in audit features. Such features require resources and need to be considered at conceptual design.<br><br></div><div>&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 12:56:09 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248466427</guid>
      </item>
      <item>
         <title>NOOR FARHANOM BINTI NAZARUDIN (BB15110467)</title>
         <author>anomnazarudin96</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248468634</link>
         <description><![CDATA[<div><strong>System Analysis<br>1)</strong><em><mark>Analysis of current system achievement</mark></em><mark><br></mark>&nbsp;Current systems analysis technique is used to evaluate the degree of support provided by current systems to the business activities of the enterprise. Assessments of user and technical satisfaction are performed and data, procedures and problems are analyzed. <br>&nbsp;The purpose of current systems analysis technique is to identify shortcomings and issues with current systems. It is used to assess the usefulness, usability, and overall user satisfaction with the current systems to facilitate decision making concerning the current systems’ strategic and tactical viability. <br>Besides,&nbsp; the current systems analysis technique provides a comprehensive and objective method for assessing current systems.<br><br><a href="https://www.projectmanagement.com/process/popup.cfm?ID=23401">https://www.projectmanagement.com/process/popup.cfm?ID=23401</a><br><br><em><mark>&nbsp;2) Analysis of a system’s user needs<br></mark></em>&nbsp;A good set of user requirements are needed for any project, especially computer system projects, to be successful. This is where many projects fail, in that they do not specify correctly what the system should do. In fact many systems have just been given a deadline for delivery, a budget to spend, and a vague notion of what it should do.&nbsp;<br><br>&nbsp;</div><div>As you start to specify what you want or desire, you hit up against technical language of requirements. Fear not, this is quite straightforward:</div><ul><li><strong>Functional requirements</strong> - are what you want a system to do.</li><li><strong>Non-functional requirements</strong> - are restrictions on the types of solutions that will meet the functional requirements.</li><li><strong>Design objectives</strong> - Are the guides to use in selecting a solution.&nbsp;</li></ul><div><a href="https://www.coleyconsulting.co.uk/require.htm">https://www.coleyconsulting.co.uk/require.htm</a><br><br><em><mark>3) Information gathering techniques<br></mark></em>The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:<br><br></div><ul><li><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.</li><li><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.</li><li><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.</li><li><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks.&nbsp;</li></ul><div><a href="https://project-management-knowledge.com/definitions/i/information-gathering-techniques/">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a><br><br><em><mark>4) System’s analysis report<br></mark></em>&nbsp;The analysis team, at the end of this phase, produces a document containing the functional requirements of the new computer information system. Additionally, the document contains preliminary schedules and a budget for the next phase. The task force or committee responsible for the project studies the document for the purpose of approving or not approving the work of the analysis team. In addition, the analysis team provides the committee with a demonstration. In essence, the analysis team walks the committee members, step by step, through the requirements definition phase. If the committee approves this phase, then the analysis team is funded and given the go-ahead to proceed to the next phase. However, if the committee does not approve this phase, then either the project is canceled or, after appropriate modifications, the analysis team resubmits a new document to the committee.<br><br>Read more: <a href="http://www.referenceforbusiness.com/management/Str-Ti/Systems-Analysis.html#ixzz5Bi81q9Jk">http://www.referenceforbusiness.com/management/Str-Ti/Systems-Analysis.html#ixzz5Bi81q9Jk</a> <br><br><em><mark>5) Accountant role in systems analysis&nbsp;</mark></em></div><div>&nbsp; Besides traditional accounting knowledge, accountants need to possess other skills that are vital to their survival in an effective organization. Among those skills are knowledge sharing, the understanding of information systems design, systems development, and applications. One of the systems issues that accountants face is the implementation and maintenance of ERP (Enterprise resources planning) systems in the organization. ERP systems allow companies to integrate at all levels and to utilize important ERP application such as supply-chain management, accounting application, human resource and customer relationship management (Boubekri, 2001). <br>Read more:<br><a href="https://dl.acm.org/citation.cfm?id=1168392">https://dl.acm.org/citation.cfm?id=1168392</a><br><strong><br>System Design <br></strong><em><mark>1) User interface design<br></mark></em>&nbsp;User Interface (UI) Design focuses on anticipating what users might need to do and ensuring that the interface has elements that are easy to access, understand, and use to facilitate those actions. UI brings together concepts from <a href="https://www.usability.gov/what-and-why/interaction-design.html">interaction design</a>, <a href="https://www.usability.gov/what-and-why/visual-design.html">visual design</a>, and <a href="https://www.usability.gov/what-and-why/information-architecture.html">information architecture</a>. <br><br><a href="https://www.usability.gov/what-and-why/user-interface-design.html">https://www.usability.gov/what-and-why/user-interface-design.html</a><br><br><em><mark>2) Output Design<br></mark></em>&nbsp;The objectives of input design are :</div><ul><li>To develop output design that serves the intended purpose and eliminates the production of unwanted output.</li><li>To develop the output design that meets the end users requirements.</li><li>To deliver the appropriate quantity of output.</li><li>To form the output in appropriate format and direct it to the right person.</li><li>To make the output available on time for making good decisions.</li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br></div><div><em><mark>3) Input design<br></mark></em>&nbsp;In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.<br><br></div><div>Therefore, the quality of system input determines the quality of system output. Welldesigned input forms and screens have following properties :</div><ul><li>It should serve specific purpose effectively such as storing, recording, and retrieving the information.</li><li>It ensures proper completion with accuracy.</li><li>It should be easy to fill and straightforward.</li><li>It should focus on user’s attention, consistency, and simplicity.</li><li>All these objectives are obtained using the knowledge of basic design principles regarding :<ul><li><em>What are the inputs needed for the system?</em></li><li><em>How end users respond to different elements of forms and screens.</em></li></ul></li></ul><div><a href="https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm">https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm</a><br><br><em><mark>4) Security and control measures <br></mark></em>There are three types of security controls, as follows:</div><ul><li><em>Management controls</em>: The security controls that focus on the management of risk and the management of information system security.</li><li><em>Operational controls</em>: The security controls that are primarily implemented and executed by people (as opposed to systems).</li><li><em>Technical controls</em>: The security controls that are primarily implemented and executed by the system through the system's hardware, software, or firmware.&nbsp;</li></ul><div><a href="https://developer.mozilla.org/en-US/docs/Web/Security/Information_Security_Basics/Security_Controls">https://developer.mozilla.org/en-US/docs/Web/Security/Information_Security_Basics/Security_Controls</a><br><br><em><mark>5) Accountant role in systems designing&nbsp;<br></mark></em>&nbsp;The role of accountant has expanded due to the development of the accounting information of various business sectors, on the one hand, and the increase of the volume and the complexity of the information, on the other hand; the accountant shall play an active and effective role in the processes of designing the systems in order to achieve an effective internal system as well as the needs of accounting information users. There is no doubt the success of developing the system requires the necessity of participation of accountants in establishing and developing that system. The effective method of applying the participation principle is represented by the ability of system to involve the accountants not only in one stage of the development of the system but all stages of system development.<br><a href="http://bepls.com/beplsoctober2015/19.pdf">http://bepls.com/beplsoctober2015/19.pdf</a><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 13:02:12 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248468634</guid>
      </item>
      <item>
         <title>NURASHILA NADIRAH BINTI AZMAN BB15110554</title>
         <author>Nurashila</author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248488775</link>
         <description><![CDATA[<div><strong>System analysis and design</strong></div><div><strong>System analysis<br></strong><br></div><div><strong>1. Analysis of current achievement system</strong></div><div><br></div><div>Systems analysis is a process of collecting factual data, understand the processes involved, identifying problems and recommending fea- sible suggestions for improving the system functioning. This involves studying the business processes, gathering operational data, un- derstand the information flow, finding out bottlenecks and evolving solutions for overcoming the weaknesses of the system so as to achieve the organizational goals. System Analysis also includes sub- dividing of complex process involving the entire system, identifica- tion of data store and manual processes.&nbsp;</div><div>The major objectives of systems analysis are to find answers for each business process: What is being done, How is it being done, Who is doing it, When is he doing it, Why is it being done and How can it be improved? It is more of a thinking process and involves the creative skills of the System Analyst. It attempts to give birth to a new effi- cient system that satisfies the current needs of the user and has scope for future growth within the organizational constraints. The result of this process is a logical system design. Systems analysis is an iterative process that continues until a preferred and acceptable solution emerges.&nbsp;</div><div><br><br></div><div><a href="https://hepiprayudi.files.wordpress.com/2018/03/romney_ab-az-ch18_upload.pptx">http://download.nos.org/cca/cca1.pdf</a></div><div><br></div><div><br></div><div><strong>2. Analysis of a system's user needs</strong></div><div><br></div><div>User needs and requirements provide essential information concerning the development and construction of any system to assure that the developed system meets the stated needs of the originating organization. The acquisition and articulation of this information is the most critical part of a systems development process and may be especially difficult due to the very complexity of the process of acquiring and analyzing user needs and requirements. Collection and analysis of information must be correct, consistent and unambiguous. Added to this complexity is the question of being certain that the information may be validated and accessible to those from the community of interest. A process to develop user needs and requirements to meet these attributes is fundamental. User needs and requirements for life support systems, initiated by user determination that a need exists that is not met by existing systems, require such a disciplined approach. System level requirements are developed to broadly outline the desired capabilities, which, in turn, are investigated to ascertain feasibility and practicality and examine trade-offs. Once the feasibility and practicality of the desired system have been determined to be necessary and sufficient to launch a new system (or significant modification of an existing or legacy system), the resulting specifications are analyzed for errors and any errors found are resolved, difficult or incomplete concepts are prototyped, and the final product is transformed to formal or semi-formal languages of a specification. The resulting product is an acceptable set of user needs and requirements.&nbsp;</div><div><br><br></div><div><a href="https://pdfs.semanticscholar.org/c679/2dda33945ab135bb232b555a73c5896866d8.pdf">https://pdfs.semanticscholar.org/c679/2dda33945ab135bb232b555a73c5896866d8.pdf</a><br><br><br><strong>3. Information gathering technique</strong></div><div><br></div><div>Managing information involves gathering and distributing necessary information and assimilating them on the project management activities and processes. The information gathering techniques are repeated processes that are used to create and organize data across different kinds of sources. There are four types of information gathering techniques as follows:</div><ul><li><a href="https://project-management-knowledge.com/definitions/b/brainstorming-technique/">Brainstorming</a>: This method is used to get a list of all project lists. All ideas are generated with the help of a facilitator through an open discussion and mass interviewing techniques. Commonly, the brainstorming technique can be done during a scheduled meeting with peers, individual brainstorming, or even at an informal meeting.</li><li><a href="https://project-management-knowledge.com/definitions/d/delphi-technique/">Delphi technique</a>: This technique in project management requires the presence of a facilitator that gives out questionnaires to solicit different ideas. The responses are summarized and recirculated to the participants.</li><li><a href="https://project-management-knowledge.com/definitions/r/root-cause-analysis/">Root cause analysis</a>: One of the information gathering techniques is the root cause analysis. It is used in identifying problems and its underlying causes thus developing a preventive action.</li><li><a href="https://project-management-knowledge.com/definitions/i/interviews/">Interviewing</a>: Stakeholders, participants, and experts are interviewed to identify risks.</li></ul><div><br><br></div><div><a href="https://hepiprayudi.files.wordpress.com/2018/03/romney_ab-az-ch18_upload.pptx">https://project-management-knowledge.com/definitions/i/information-gathering-techniques/</a><br><br><br><strong>4. System's analysis report<br><br></strong>System analysis report provides the detailed analyses that support a System Evaluation Report (SER). It accounts for all issues and measures contained in the System Evaluation Plan. A SAR is also prepared to support a System Assessment (SA) when the analysis is too detailed or inappropriate for inclusion in the SA and addresses only those issues and measures contained in the SA.<br><a href="https://definedterm.com/system_analysis_report">https://definedterm.com/system_analysis_report</a><br><br><br><strong>5. Accountant role in system analysis</strong><br><br>•Accountants also play an important role in systems development:</div><div>–As AIS users, they must determine their information needs and systems requirements and communicate them to system developers.</div><div>–As members of project development teams or steering committees, they help management in the development process.</div><div>–They are also active in:</div><div>•Designing system controls and monitoring and testing these controls.</div><div>•Ensuring the system is easy to audit.</div><div>–Controls and “auditability” need to be built in early to minimize costs and inefficiencies later.</div><div><br></div><div>https://hepiprayudi.files.wordpress.com/2018/03/romney_ab-az-ch18_upload.pptx<br><br><strong>System design<br><br>1. User interface design</strong><br><br>What is User Interface (UI) Design?</div><div>User interface (UI) design is the design of user interfaces for software or machines, such as the look of a mobile app, with a focus on ease of use and pleasurability for the user. UI design usually refers to the design of graphical user interfaces—but can also refer to others, such as natural and voice user interfaces.</div><div>Since software is intangible, the only way a user can control or interact with it is through a designed user interface. A well-designed user interface creates a user experience that the designer intended and/or a user experience that the user appreciates.&nbsp;</div><div>Many user interfaces are designed with a focus on usability and efficiency. Users should be able to achieve their goals as efficiently as possible, without focusing too much on the user interface itself. In that sense, a well-designed user interface becomes effectively invisible to those using it. In other words, they interact directly with the ‘reality’ the design portrays without reckoning on the point that, for example, thumbing button icons through the glass screens of their handheld devices is responsible for producing changes in what they see. However, usability and efficiency might not be the only measure of a well-designed user interface; a user interface might be designed to create a fun and pleasurable experience for users instead (e.g., in games).</div><div>At the other end of the spectrum, designers can—unethically—deliberately design user interfaces that are confusing—in order to trick users into purchasing or signing up for things they might not be interested in. These user interfaces are known as dark patterns. Examples of dark patterns include add-ons that are included by default (e.g., additional luggage allowance when booking air tickets), and intentionally complicated processes meant to deter users (e.g., long and confusing pages to unsubscribe from email newsletters).</div><div><br></div><div>https://www.interaction-design.org/literature/topics/ui-design<br><br><br><strong>2. Output design </strong><br><br>Output Design</div><div>The design of output is the most important task of any system. During output design, developers identify the type of outputs needed, and consider the necessary output controls and prototype report layouts.</div><div>Objectives of Output Design</div><div>The objectives of input design are −</div><div>* To develop output design that serves the intended purpose and eliminates the production of unwanted output.&nbsp;</div><div>* To develop the output design that meets the end users requirements.&nbsp;</div><div>* To deliver the appropriate quantity of output.&nbsp;</div><div>* To form the output in appropriate format and direct it to the right person.&nbsp;</div><div>* To make the output available on time for making good decisions.&nbsp;</div><div><br></div><div>https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm<br><br><br><strong>3. Output design</strong>&nbsp;<br><br>Input Design</div><div>In an information system, input is the raw data that is processed to produce output. During the input design, the developers must consider the input devices such as PC, MICR, OMR, etc.</div><div>Therefore, the quality of system input determines the quality of system output. Welldesigned input forms and screens have following properties −</div><div>* It should serve specific purpose effectively such as storing, recording, and retrieving the information.&nbsp;</div><div>* It ensures proper completion with accuracy.&nbsp;</div><div>* It should be easy to fill and straightforward.&nbsp;</div><div>* It should focus on user’s attention, consistency, and simplicity.&nbsp;</div><div>* All these objectives are obtained using the knowledge of basic design principles regarding −</div><div>&nbsp; &nbsp; * What are the inputs needed for the system?&nbsp;</div><div>&nbsp; &nbsp; * How end users respond to different elements of forms and screens.&nbsp;</div><div>Objectives for Input Design</div><div>The objectives of input design are −</div><div>* To design data entry and input procedures&nbsp;</div><div>* To reduce input volume&nbsp;</div><div>* To design source documents for data capture or devise other data capture methods&nbsp;</div><div>* To design input data records, data entry screens, user interface screens, etc.&nbsp;</div><div>* To use validation checks and develop effective input controls.&nbsp;</div><div><br></div><div>https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_design_input_output_forms.htm<br><br><br><strong>4. Security and control measure</strong><br><br>Security controls are technical or administrative safeguards or counter measures to avoid, counteract or minimize loss or unavailability due to threats acting on their matching vulnerability, i.e., security risk. Controls are referenced all the time in security, but they are rarely defined. The purpose of this section is to define technical, administrative/personnel, preventative, detective, and corrective compensating controls, as well as general controls.</div><div><br></div><div>https://www.sans.edu/cyber-research/security-laboratory/article/security-controls<br><br><br><strong>5. Accountant role in system design</strong><br><br>Accountants are major catalysts in the design of accounting information system. They are the most suitable and most equipped information measurement professionals to design the information system. It is generally believed that insiders in every area of life make better developmental instrument. This function of designing AIS includes the design of managerial accounting information system to aid management in decision making processes.&nbsp;</div><div>An appreciation of the accountant’s responsibility for system design requires a historic perspective that predates the computer as a business information tool. Traditionally, accountants have been responsible for key aspects of the information system, including assessing the information needs of users, defining the content and format of output reports, specifying sources of data, selecting the appropriate accounting rules, and determining the controls necessary to preserve the integrity and efficiency of the information system.&nbsp;</div><div>These traditional systems were physical, observable, and unambiguous. The procedures for processing information were manual, and the medium for transmitting and storing data was paper. With the arrival of the computer, computer programs replaced manual procedures, and paper records were stored digitally. The role accountants would play in this new era became the subject of much controversy. Lacking computer skills, accountants were generally uncertain about their status and unwilling to explore this emerging technology.&nbsp;</div><div>Many accountants relinquished their traditional responsibilities to the new generation of computer professionals who were emerging in their organizations. Computer programmers, often with no accounting or business training, assumed full responsibility for the design of accounting information systems. As a result, many systems violated accounting principles and lacked necessary controls. Large system failures and computer frauds marked this period in accounting history. By the mid-1970s, in response to these problems, the accounting profession began to reassess the accountant’s professional and legal responsibilities for computer-based systems.&nbsp;</div><div>Today, we recognize that the responsibility for systems design is divided between accountants and IT professionals as follows: the accounting function is responsible for the conceptual system, and the IT function is responsible for the physical system. To illustrate the distinction between conceptual and physical systems, consider the following example:&nbsp;</div><div>The credit department of a retail business requires information about delinquent accounts from the AR department. This information supports decisions made by the credit manager regarding the creditworthiness of customers.&nbsp;</div><div>The design of the conceptual system involves specifying the criteria for identifying delinquent customers and the information that needs to be reported. The accountant determines the nature of the information required, its sources, its destination, and the accounting rules that need to be applied. The physical system is the medium and method for capturing and presenting the information. The computer professionals determine the most economical and effective technology for accomplishing the task. Hence, systems design should be a collaborative effort. Because of the uniqueness of each system and the susceptibility of systems to serious error and even fraud, the accountant’s involvement in systems design should be pervasive.&nbsp;</div><div><br></div><div><br></div><div>http://bepls.com/beplsoctober2015/19.pdf</div><div><br></div><div><br><br></div><div><br></div><div><br></div><div><br><br></div><div><br></div><div><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 13:45:02 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248488775</guid>
      </item>
      <item>
         <title>NURUL AZIRA BINTI MACHAMUD BB1510584</title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248491058</link>
         <description><![CDATA[<div>&nbsp;</div><div><strong>System Analysis</strong>&nbsp;<br><br>1.&nbsp; &nbsp; &nbsp; &nbsp;Analysis of current system achievement<br><br></div><div>To analysis of current system achievement are by using a tools and techniques. The purpose is to identify improvements of the system and to set a features and requirements for a new system. The tools and techniques including Data Dictionary, Data Flow Diagram, Decision Tree, Decision Tables, Structured English and Pseudocode. &nbsp;</div><div>&nbsp;</div><div>2.&nbsp; &nbsp; &nbsp; <strong>&nbsp;</strong>Analysis of a system’s user needs</div><div><strong>&nbsp;</strong></div><div>To analysis system’s user need, at the development process, a staff of IT will collect information from users, describe the need of system and build the new system. User-oriented systems is applied and they is needs to be involves at system development stages.&nbsp;</div><div>&nbsp;</div><div>3.&nbsp; &nbsp; &nbsp; Information gathering technique&nbsp;</div><div>&nbsp;</div><div>Technique use to get information on system analysis is by using interview. Interview is done to get information from someone by setting a meeting. A knowledge is have so can plan, conduct, document and make interviews successful. There are 7 steps of interview which is&nbsp;</div><div>&nbsp;</div><div>1. Determine the people to interview.&nbsp;</div><div>2. Set the interview objectives.&nbsp;</div><div>3. Make questions of interview.&nbsp;</div><div>4. Interview preparation.&nbsp;</div><div>5. Interview conduct.&nbsp;</div><div>6. Interview documentation.&nbsp;</div><div>7. Interview evaluation&nbsp;<br><br></div><div>Other techniques is fact-finding techniques which is review the document, observation, surveys, research, questionnaires and sampling.&nbsp;<br><br></div><div>4.&nbsp; &nbsp; &nbsp; System’s analysis report&nbsp;<br><br></div><div>System analysis report is for project’s major stakeholder including academic supervisor, team and student. It is highlight the system vision to business benefit.&nbsp;<br><br></div><div>5.&nbsp; &nbsp; &nbsp; Accountant role in system analysis&nbsp;</div><div>The role of accountant in system analysis to make sure only used cost is includes in cost measurement. Other, accountant set realistic useful life of assets.&nbsp;<br><br><br><br>&nbsp;</div><div><strong>System Design </strong><br><br></div><ol><li>&nbsp;User interface design</li></ol><div>User interface design explain about how users communicate with system of computer and includes software, hardware, output, menus, functions and features influences two way communication between computer and user.&nbsp;<br><br></div><div>2.&nbsp; &nbsp; &nbsp; Output design&nbsp;</div><div>The questions to think before designing output are:&nbsp;</div><div>-What is the output purpose?&nbsp;</div><div>-For who the information, needed purposes and how can it use?&nbsp;</div><div>-What is a specific purpose?&nbsp;</div><div>-The output need to be print out or screen reading?&nbsp;</div><div>-When the information need to be provide, is it need to be often update and how often?&nbsp;</div><div>&nbsp;</div><div>3.&nbsp; &nbsp; &nbsp; Input design&nbsp;</div><div>It takes the work statement, determination plan that required, analysis of current situation and requirements of proposed system includes conceptual data model, Metadata and modified DFDs.&nbsp;</div><div>&nbsp;</div><div>4.&nbsp; &nbsp; &nbsp; Security and control measures&nbsp;</div><div>Company are used various control including output control methods to sustain the security and integrity of output. Such as, any report should have tittle, date, time, code or number that appropriate. To identified it, the report it should have labelled. It should be audited by selected random to check the completeness and correctness.&nbsp;</div><div>On the other hand, to protect data of company from unauthorized access and theft, a company must have protects privacy rights. The company can perform several tasks to ensure the output security such as printed can copy but have the limit number.&nbsp;</div><div>&nbsp;</div><div>5.&nbsp; &nbsp; &nbsp; Accountant role in Systems Design&nbsp;</div><div>Accountant is a major role play in system design as a catalyst. He has a professional requirement to design the information system. &nbsp;<br>&nbsp;<br>&nbsp;References&nbsp;</div><div>1.&nbsp; &nbsp; &nbsp; Shelly, G. B., &amp; Rosenblatt, H. J. (2011). Systems Analysis and Design Ninth Edition.&nbsp;</div><div>2.&nbsp; &nbsp; &nbsp; Dennis, A., Wixom, B. H., &amp; Tegarden, D. (2015). <em>Systems analysis and design: An object-oriented approach with UML</em>. John wiley &amp; sons.&nbsp;</div><div>3.&nbsp; &nbsp; &nbsp; Awodele, O., Onuiri Ernest, E., &amp; Olaore Olufunmike, A. (2015). A Real-Time Crime Records Management System For National Security Agencies. <em>European Journal Of Computer Science And Information Technology</em>, <em>3</em>(2), 1-12.&nbsp;</div><div>4. <a href="https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php">https://www.ukessays.com/essays/information-systems/system-analysis-report-7597.php</a><strong><br></strong><br></div><div>&nbsp;<br><br></div><div>&nbsp;<br><br></div><div>&nbsp;<br><br></div><div>&nbsp;<br><br></div><div><br><br><br><br><br></div><div>&nbsp;<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-04-04 13:49:44 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248491058</guid>
      </item>
      <item>
         <title>NOORFADZILAH BINTI SHAMSUDDIN BB15110469</title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248529336</link>
         <description><![CDATA[<div><a href="http://www.ddegjust.ac.in/studymaterial/mca-3/ms-04.pdf">http://www.ddegjust.ac.in/studymaterial/mca-3/ms-04.pdf</a><br>file:///C:/Users/User/Downloads/watch.htm</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/276159442/dc9405027da8482486fc306ab6bd08f5/PADLET_2_SYSTEM_ANALYSIS.docx" />
         <pubDate>2018-04-04 15:01:28 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248529336</guid>
      </item>
      <item>
         <title>Nur Muzainah Fajrina Binti Abdul Jan (BB15161025)</title>
         <author></author>
         <link>https://padlet.com/sma6/hb8a14t67qkn/wish/248540269</link>
         <description><![CDATA[]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/278869799/4205647bd4624fdc3858041b86f54a08/System_Analsyis___System_Design.docx" />
         <pubDate>2018-04-04 15:21:44 UTC</pubDate>
         <guid>https://padlet.com/sma6/hb8a14t67qkn/wish/248540269</guid>
      </item>
   </channel>
</rss>
