Find Resources & Connect with members on topics that interest you.

AI - Acquire and Implement

PO - Plan and Organize

DS - Deliver and Support

Please sign in to see your topics.

You must be logged in to join this group.

AI2.2 - Detailed Design

This topic is intended to enable collaboration and sharing of information to facilitate a better understanding and approach to implementing this COBIT control objective based on the risk, value and guidance provided by its corresponding control practices.

COBIT Control Objective AI2.2 - Detailed Design is contained within Process Popup Acquire and Maintain Application Software.

Learn more about COBIT and related publications.

Click “Join This Community” to be able to actively participate in discussions and contribute content. You must be an ISACA member to join this topic. Join ISACA now.

 
This Topic Has:
6 Members
0 Online
4976 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Badge: Energizer


Detailed Design

Prepare detailed design and technical software application requirements. Define the criteria for acceptance of the requirements. Have the requirements approved to ensure that they correspond to the high-level design. Perform reassessment when significant technical or logical discrepancies occur during development or maintenance.

View value and Risk Drivers  help

Hide value and Risk Drivers help


Value Drivers

  • Reduced costs
  • Efficient application coding and maintenance
  • Prioritisation on important features
  • Avoidance of data redundancy
  • Application meeting usability requirements
  Risk Drivers
  • Processing of invalid transactions
  • Increasing costs for system redesign
  • Data in application systems processed incorrectly

View Control Practices  help

Hide Control Practices  help

  1. Classify data inputs and outputs according to information architecture and data dictionary standards.
  2. Assess the impact on existing applications and infrastructure during the process of gathering requirements and designing the solution, and design appropriate integration approaches. Address integration of the planned application system with existing or planned co-operating applications and infrastructure, including packaged software acquired from third parties. Consider the impact of differing update cycles.
  3. Specify the source data collection design, documenting the data that must be collected and validated for processing transactions as well as the methods for validation. Consider data inputs from existing programs, packaged software, external parties, web forms, etc.
  4. Define system availability requirements, and design appropriate redundancy, failure recovery and backup processing arrangements.
  5. Define file and database requirements for storage, location and retrieval of data. Consider availability, control and auditability, security, and network requirements.
  6. Define the processing steps, including specification of transaction types and processing rules incorporating logic transformations or specific calculations. Consider availability, control and auditability, logging, and audit trails.
  7. Based on the user requirements and taking into account the different types of recipients, usage, details required, frequency, method of generation and other design details, define the data requirements for all identified outputs. Appropriate design requirements should guarantee the availability, completeness, integrity and confidentiality of output data. Consider the impact of data outputs to other programs, external parties, etc.
  8. Design the interface between the user and the system application so that it is easy to use and self-documenting. Consider the impact of system-to-system interface design on infrastructure performance, including the capacity of personal computing devices and network bandwidth and availability.
  9. Reassess system design whenever significant technological and/or logical discrepancies occur during design, development and maintenance. Results of the reassessment should be subject to the normal approval cycle.
  10. Prepare and document detailed design specifications in accordance with organisational and industry-accepted specification standards and the information architecture.
  11. Conduct a design walk-through with IT and business stakeholders before development is initiated, as a part of the sign-off process for the design specifications. Various aids can be used to assist with the sign-off, including prototypes, to aid stakeholder understanding of the final design.

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 64 total

Must be a Topic member to contribute
View All »
Downloads
Posted by ISACA 1539 days ago
Books
Posted by ISACA 618 days ago
Books
Posted by ISACA 832 days ago
Books
Posted by ISACA 937 days ago

Events & Online Learning: 12 total

Journal Articles: 246 total

Volume 3, 2107
by Jayakumar Sundaram, CISA, ISO 27001 LA
The SoA is a continuously updated and controlled document that provides an overview of information security implementation.
Volume 6, 2106
by Venkatasubramanian Ramakrishnan, CISM, CRISC, CHFI
Bayesian networks can capture the complex interdependencies among risk factors and can effectively combine data with expert judgment.
Volume 3, 2018
by Sunil Bakshi, CISA, CRISC, CISM, CGEIT, ABCI, AMIIB, BS 25999 LI, CEH, CISSP, ISO 27001 LA, MCA, PMP
My organization has initiated a project to use blockchain technology. We have been hearing about this technology becoming the backbone of digital currency, but we have also heard that there are many issues related to digital currency.
Volume 3, 2018
by Ofir Eitan, CISM, CCSK, CTI
One of the major challenges chief information security officers (CISOs) face in almost any organization is prioritizing information security interests with regard to IT interests.
Volume 3, 2018
by Alex Quiles, CISA
The use of Windows accounts to authorize users to applications introduces risk that an auditor should evaluate.
Volume 3, 2018
by Kevin Alvero, CFE, Randy Pierson, CISA, and Wade Cassels, CISA, CIA, CFE, CRMA
As organizations try to keep up with rapid changes in technology, they are using acquisitions as a way to quickly develop entirely new lines of business or to simply close gaps in technological capability.

Wikis: 2 total

Blog Posts: 151 total

https://www.theguardian.com/technology/2018/may/17/cyberlaundering-funds-terror-internet-fake-transactions-cashless-society?CMP=Share_iOSApp_Other
Posted By : TafadzwaPadare | 1 comments
Hello and welcome to my first post of my new blog, 'Cybersecurity ROCKS!'.   As a long time member of the security community and new to the Vancouver area, I'd like to tell you a little about myself, how my career began and where my current passions in cy...
Posted By : cybersecgal | 1 comments
5 Jun 2018
Recently, I witnessed an interesting webcast by Scopism, an UK-based consulting and training company. They announced the publication of the SIAM(c) Foundation Body of Knowledge, available for free through their website www.scopism.com. Service Integration...
Posted By : Peter873 | 2 comments
Security in IoT environment
Posted By : Hyun239 | 0 comments
20 Apr 2018
Good day. I have an interesting situation that came about just this week.  New career opportunities are not all that they seem to be.  What I thought was going to be a great career change ended up in disaster.  With only one week and two day's, I was dism...
Posted By : Brian824 | 0 comments
La Tecnología de la Información (TI), en todas sus áreas (base de datos, seguridad de la información, desarrollo de software, redes, etc.), debe tener como objetivo primario el apoyo a los Procesos del Negocio (PN) de la organización. Sin embargo, es comú...
Posted By : emorro | 0 comments