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.7 - Development of Application Software

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.7 - Development of Application Software 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:
16 Members
0 Online
4305 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Badge: Energizer


Development of Application Software

Ensure that automated functionality is developed in accordance with design specifications, development and documentation standards, QA requirements, and approval standards. Ensure that all legal and contractual aspects are identified and addressed for application software developed by third parties.

View value and Risk Drivers  help

Hide value and Risk Drivers help


Value Drivers

  • Ensuring that business, customer and user needs are met
  • Ability to manage and prioritise resources
  • Application software creating capabilities for the business
  • Application meeting usability requirements
  Risk Drivers
  • Waste of resources
  • Lost focus on business requirements
  • High number of failures
  • Inability to maintain applications effectively

View Control Practices  help

Hide Control Practices  help

  1. Establish development procedures to ensure that the development of application software adheres to organisational development standards.
  2. Ensure that application software is developed based on agreed-upon specifications and business, functional and technical requirements.
  3. Establish agreed-upon stages of the development process (development checkpoints). At the end of each stage, facilitate formal discussions of approved criteria with the stakeholders. Obtain approval and sign-off from all stakeholders following successful completion of functionality, performance and quality reviews before finalising stage activities. At the final stage, confirm with IT technical authorities and operations management that the applications are ready and suitable for migration to the production environment.
  4. Assess the adequacy of software developed in terms of its compatibility and ease of integration with existing applications and infrastructure.
  5. When third-party developers are involved with the applications development, establish that they adhere to contractual obligations and organisational development standards and that licensing requirements have been addressed.
  6. Monitor all development activities and track change requests and design, performance and quality reviews, ensuring active participation of all impacted stakeholders, including business process users and IT technology representatives.
  7. Ensure that requested changes arising within IT or from the business process owner are tracked.
  8. Consider the effect of dynamic, non-sequential development techniques (e.g., rapid application development, extreme programming) on the monitoring of the application development progress and approval of application software by stakeholders.

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 72 total

Must be a Topic member to contribute
View All »
Downloads
Posted by ISACA 1424 days ago
Books
Posted by ISACA 503 days ago
Books
Posted by ISACA 717 days ago
Books
Posted by ISACA 822 days ago

Events & Online Learning: 15 total

Journal Articles: 240 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 1, 2018
by Steven J. Ross, CISA, CISSP, MBCP
Managing availability in a multi-modal environment requires a great deal of attention to details, which are being defined by the multi-modal pioneers of our day.
Volume 1, 2018
by Aditya K. Sood, Ph.D., and Rehan Jalil
With the robust requirements listed by upcoming regulations, such as GDPR, the importance of a cloud app security solution cannot be ignored.
Volume 1, 2018
by Sandy Fadale, CRISC, CISM, CGEIT
Get to know your network.
Volume 6, 2017
by Robert Putrus, CISM, CFE, CMC, PE, PMP
This article presents a risk-based management approach to third-party data security risk and compliance through the development of a third-party risk register.

Wikis: 2 total

Blog Posts: 149 total

Have you experienced ransomware attack so far and, if yes, what did you do to resolve? I set up Twitter poll here: https://twitter.com/DPleskonjic/status/953608717399941120 It lasts for seven days. Thank you for taking part in the poll.
Posted By : Dragan Pleskonjic | 2 comments
Bitcoin Trade a Bubble! Block Chain Technology Useful .ISACA Members whats your Take on Bitcoin Trade, Is its a bubble that wont last long.Block chain Technology is useful and its continuously growing to as form of secure record  management and secured us...
Posted By : MUGAMBI865 | 1 comments
There is no doubt with our current business environment, we will be experiencing more cyber breaches in the next few months.  The latest threat is an architectural design flaw in newer CPU's.  These design vulnerabilities could allow attackers to intercep...
Posted By : Fred586 | 1 comments
There are some math models for business that MBAs are taught. Just like assembling burgers for fast food or call wait queue management in a call center, vulnerability patching is a time based business opportunity. Leadership can be expected to use this ...
Posted By : Don Turnblade | 1 comments
My personal thoughts after listening to C-level executives at the CxO Roundtable Series sponsored by Intel, IBM, HyTrust & ReedSmith. For an invite, please reach out to me. Data Protection under the GDPR For past few months, I’ve been helping to org...
Posted By : Thomas152 | 1 comments
I predict that on 1 July 2018, I will be calmly eating a barbecue sandwich, talking with friends and possibly, I will burn a copy of the RFC2246: TLS version 1.0 standard for entertainment value.  Those will less effective Vendor, Network, Systems, Applic...
Posted By : Don Turnblade | 0 comments