About Systems Development

9 Pages   |   1,728 Words
Contents
Introduction. 3
Approach to Systems Development. 3
Comparison between the use of SDLC and Agile development. 3
Justification. 4
Systems Requirements. 4
Primary functional requirements. 4
Non-functional Requirements. 4
Project cost/benefit analysis. 5
Project schedule. 5
System Information Requirement Investigation Techniques. 6
Reflections and Conclusions. 7
Bibliography. 8
 

Introduction

The aim of the report is to carry out analysis and develop the critical specifications for an automated information system. This would essentially be carried out through an analysis of SDLC and agile development, as well as identifying the primary functional requirements and the non-functional requirements for the particular system utilized at FC. The objectives of this report pertain to the various building blocks i.e. the cost benefit analysis, project schedule, and the techniques pertaining to system information requirement investigation. Furthermore, in light of the aims and objectives, the achievements and constraints can be highlighted to depict the essence of the report.   

Yes, We Can Help!

We promise to deliver high quality papers on time which will improve your grades. Get help now!

SAMPLES PLACE ORDER OUR SERVICES
Plagiarism Free Work
Best Price Guarantee
100% Money Back Guarantee
Top Quality Work

Approach to Systems Development

Comparison between the use of SDLC and Agile development

The comparison pertaining to the two methodologies can be based on the strengths and weakness of the usage of each method (Biswas, 2014):
Strengths Weaknesses
SDLC
Enhanced Documentation User input may in some cases be limited
Detailed Steps to follow High development cost
Easy maintenance Increased time consumption in development
High level of control Rigid
Useful to monitor large projects The system must be defined at commencement
Can be useful in case of evaluating completion and cost targets Cost estimation is tedious and may lead to project overruns
Volatility in MIS staffing can be tolerated  
User input is well defined  
High standards of design and development  
Agile Development
Adherence to late changes Only senior programmers can undertake pertinent decisions
Flexible Project can run off-track in light of miscommunications regarding final goals
Superior ROI Uncertainty pertaining to software deliverables at the preamble of the development lifecycle
Risk averse Emphasis pertaining to documentation and design is lacking
Continuous delivery of working software  
Short development cycle  
High productivity  
Sustainable development environment  
Builds trust and relationship  
Addresses the needs of business and realities of software development  
 

Justification

Agile SDLC makes more sense in this scenario keeping in consideration the business strategy of FC, project type, intricacy of software required, geographical situation, and team size (Turk & Vijayasarathy, 2012). The complexity of the software is very limited with the key tasks entailing the backup of settlement files, keeping track of past and current documents for the last seven years, and keeping record of meetings and milestones pertaining to the conveyance process (Williams, 2010). Furthermore, agile SDLC is more appropriate for small-medium project development. 

Systems Requirements

System requirements entail functional and non-functional requirements, whereby functional requirements depict the aspects that must be performed in accordance to the use case (Biswas, 2014). The non-functional requirements are essentially qualities that the system must possess to provide a flexible and standard context of processing, which must cater to any sort of contingencies (Biswas, 2014).

Primary functional requirements

Req U.1.1 System creates a new file for a new client, saving client information
Req U.1.2 System records the date of purchase of property
Req U.1.3 System receives a signed contract copy
Req U.1.4 System runs a Title Search to ensure no mistakes exist compared to contract details
Req U.1.5 System runs a Plan Search to ensure no mistakes exist compared to contract details
Req U.1.6 System records ‘subject to finance’, ‘Day contract goes unconditional’, ‘Settlement date’ and ‘pest and building inspections’ details
Req U.1.7 System saves deadlines and ensures tracking
Req U.1.8 System sends prepared documents to seller’s solicitors
Req U.1.9 System checks searches in case of amendments to the contract
Req U.2.0 System sends final letters to client to confirm settlement details.
Req U.2.1 System sends tax invoice to client

Non-functional Requirements

Req U.2.2. System shall be secure
Req U.2.3 System shall have sufficient network bandwidth
Req U.2.4 System shall have backup capability
Req U 2.5 System shall have the quality of disaster recovery

Project cost/benefit analysis

The project cost has been divided into development costs and implementation costs. The development costs has been identified as $65000, which is basically an estimate concluded by identifying various sources (Lee, Cheng, & Balakrishan, 2013) (Gharehchopogh & Khalifelu, 2012), whereby $21,666 were identified to be each of the 3 developers cost. The overheads and implementation cost has been identified as $75,000, which is an estimate considering the complexity of the software. The benefits include paper saving, manual entry costs, and intangible benefits. Paper saving pertains to the shift from paper to virtual interface, which implies the elimination of paper costs. One 500 page pack costs almost $2.06, whereby the assumption undertaken here is that FC works on almost a 100 cases every year, and each case requires almost 500 pages during the entire process. The total saving comes out to be $103000. The previous process required individuals to manually save information and compile them for the last 7 years, which has been assumed to be allotted to 3 individuals in various departments, and the total cost in this case was $50,000, which can now be saved. Lastly, certain intangible benefits can also be reaped from this implementation, i.e. FC brand name proliferation as a developing entity in its field. The net analysis depicts a profit of almost $33,000, albeit numerous assumptions have been undertaken, there is no doubt that in the long run, as the costs are recovered, this process would be profitable.         

Project schedule

   
TASKS Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9  
A                    
B                    
C                    
D                    
E                    
F                    
G                    
  A Conception This pertains to the initial brainstorming and conception of software framework, building on investigation results
  B Initiation This depicts the initiation of building an operational blueprint 
  C Analysis This pertains to analyzing the data available and the client requirements
  D Design Designing the software framework
  E Construction The core task of coding and construction
  F Testing The software is tested for bugs
  G Deployment The software is deployed in the clients business framework
                           
The project schedule provides a reasonable framework because it follows the Agile SDLC framework, which can be identified from the various stages of the process. The system goals have been set apart across 9 week duration, whereby the system requirements would be adequately followed in light of the analysis stage, whereby the client requirements shall be contrasted with key business aspects and streamlined against the scope of the software development process.

System Information Requirement Investigation Techniques

The stakeholders involved in this project includes FC’s client, the buyer or seller, the solicitors of both parties involved, the software engineers, the bankers or the client’s financiers, and the financier of the other party involved.
The three key techniques for conducting investigation within the context of system analysis or system information requirement analysis are observation, document analysis, and interviews (Loukis & Charalabidis, 2013). Observations tend to be the primary method involved in most project management procedures, whereby the operational aspect in analyzed as it is performed. The analyst tends to identify how the procedure is carried out within the confines of the existing system. On the other hand, interviews provide a great opportunity for a face-to-face analysis of pertinent facts, which tend to carry more weight when investigated from the users of the system (Gorla & Somers, 2014). The process takes place in terms of certain questions being asked by the interviewer, whereby the interviewee answers them to the best of their knowledge. The third key technique of investigation is the document analysis, which entails examination of records, data, procedure manuals, and documentation used with respect to the existing system (Loukis & Charalabidis, 2013). A comparison of the three in light of their advantages and drawbacks may provide a clearer picture of their importance.
Method Advantages Drawbacks
Observation
  • Data is more accurate and is collected in real time
  • Realistic review
  • Allows observing the actual methods of procedure and working
  • People may act in a different way under direct observation
  • Expensive and time consuming
  • Certain frequent problems may not occur at the time of direct observation
Interview
  • Spontaneous clarification of answers
  • Flexibility
  • Direct contact
  • Quality of information may be enhanced and interviewee confidence may be gained
  • Limited suitability in case of a large number of users or respondents
  • Certain people may refuse to give pertinent information
  • Expensive and time consuming
  • Interviewer may not be skilled in the process of interviews and may lead to collecting insufficient and inaccurate answers
Document Analysis
  • Faster and quick way to accumulate useful information
  • The source of information already exists
  • Documentation of high priority may not exist or may have been lost
  • Documentation may be insufficient
 

Reflections and Conclusions

In light of the above report, it has been successfully identified that agile SDLC is a pertinent framework for highlighting small-medium entities, whereby the process has been identified as conception, initiation, analysis, design, construction, testing, and deployment. This aspect has been utilized across a 9 week framework to completion of the project, as depicted from the Gantt chart. Three pertinent investigation methodologies have also been highlighted as observations, interviews, and document analysis. These techniques allow the consultants to have a better idea of the issues being faced and then they can better align the solution to those problems in light of client requirement specification file. However, constraints were faced in the cost-benefit analysis segment pertaining to estimates of costs and benefits to be allocated. 
 

Bibliography

Biswas, K. (2014). Chapter 3 - Technology Basics—An Introduction. Information and Software Technology, Volume 56, Issue 5, 506-515.
Gorla, N., & Somers, T. M. (2014). The Impact of IT Outsourcing on Information Systems Success . Information & Management, Volume 51, Issue 3, 320-335.
Loukis, E. N., & Charalabidis, Y. K. (2013). An Empirical Investigation of Information Systems Interoperability Business Value in European Firms. Computers in Industry, Volume 64, Issue 4, 412-420.
Turk, D., & Vijayasarathy, L. (2012). Drivers of Agile Software Development Use: Dialectic Interplay between Benefits and Hindrances . Information and Software Technology, Volume 54, Issue 2, 137-148.
Williams, L. (2010). Agile Software Development Methodologies and Practices. Advances in Computers, Volume 80, 1-44. 

Appendix

         
Cost-Benefit Analysis Software Development
Costs       $
Development Costs     65,000
Implementation Costs and operational costs 75,000
Total Costs     140,000
Benefits        
Paper Saving     103000
Manual entry costs     50,000
Intangible Benefits     20,000
Total Benefits     173,000
         
Benefits minus costs   33,000

Download Full Answer

Order Now