CA FINAL ISCA CLASSES : Chapter 5 Acquisition, Development & Implementation of Information Systems

System Development Life Cycle
Memory Technique | Shortcuts | Mnemonics


Video classes will be available for download & for streaming after the Mnemonics

The topics we are going to cover in this post are listed below:

5.5 System Development Life Cycle (SDLC)

  1. Preliminary Investigation
  2. Systems Requirement Analysis
  3. Systems Design
  4. Systems Acquisition
  5. Systems Development
  6. Systems Testing
  7. Systems Implementation
  8. Post Implementation Review and Maintenance
Mnemonic to learn this:

Link: Architect वाला i.e Architect घर को Phases मे बनता है। 


सबसे पहले Architect plot की Investigation करता है : Preliminary Investigation
फिर घर वालो से उनकी Requirement पूछता है कि कैसा घर चाहिए : System Requirement Analysis
पूछने के बाद Map Design करता है : Systems Design
अब Map बन गया तो घर बनाने का सामन का Acquisition करेगा (cement,bricks etc.) :Systems Acquisition
सामान खरीदने के बाद अब घर Develop करेगा : Systems Development
अब Architect Testing करेगा घर की के सब सही बना है ना: Systems Testing
घर वाले रहने आएंगे अब i.e Implementation होगा घर का : Systems Implementation
रहने के बाद थोड़ी बहुत Maintenenace करवानी पड़ती है  : Post Implementation Review & System Maintenance

5.5.1 Preliminary Investigation

The heading which we are going to learn on this topic are as follows:

  1. Identification of Problem
  2. Identification of Objective
  3. Delineation of Scope
  4. Feasibility Study
  5. Reporting results to Management
  6. Internal Control Aspects

Mnemonics in Hindi to easily learn this topic are given as under:

Link: पडोसी की बीवी वाला 


पडोसी की बीवी Problem मे थी
उसे बचाना मेरा Objective था
मे periscope ले के गया देखने के क्या चल रहा है
देख के पता चला कि मेरे लिए Feasible नहीं है इस situation मे हेल्प करना
मेने पुलिस मे Report कर दी
पुलिस ने आ कर Control कर ली situation

5.5.1 (iii) Delineation of Scope

The scope of a solution defines its typical boundaries. It should be clear and comprehensible to the user management stating the extent and 'what will be addressed by the solution and what Will not. Often, the scope becomes a contentious issue between development and user organizations. Hence, outlining the scope in the beginning is essential and proves quite handy. The typical scope determination may be performed on the following dimensions:

  • Functionality Requirements: What functionalities will be delivered through the solution? 
  • Data to be Processed: What data is required to achieve these functionalities? 
  • Control Requirements: What are the control requirements for this application? 
  • Performance Requirements: What level of response time, execution time and throughput is required? Constraints: What are the conditions the input data has to conform to? For example, what is the maximum number of characters that a name can have in a database? 
  • Interfaces: Is there any special hardware/software that the application has to interface with? For example-Payroll application may have to capture from the attendance monitoring system that the company has already installed. Then the solution developer has to understand the format of data, frequency mode of data transfer and other aspects of the software. 
  • Reliability requirements: Reliability of an application is measured by ts ability to remain uncorrupted in the face of inadvertent/deliberate misuse and probability of failure-free operations. The reliability required for an application depends on its criticality and the user profile. 

Mnemonics/Memory Technique to learn the above topic is given below:


Hema Malini एक Function मे गयी थी
अपनी performance देने
वहां पर कुछ MLAs बैठे थे जो कि हेमा जी को Reliable नहीं लगे
उन्होंने बोला MLA को तुम्हारा खुद पे Control नहीं है
अब Organisor ने बोलै आप चिंता न करे
सबका ID चेक होगा
आपके साथ Bouncers भी होंगे (Constraints)
जिससे आपका किसी के साथ interface नहीं हो पायेगा 

Video Classes for the above topics are here: