Find Resources and 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.

Subscribe to this discussion

SDLC Best Practices

Does anyone have any great resources for SDLC (System Development Life Cycle) for implementing a new financial accounting software?
You must sign in to rate content.
(Unrated)

Comments

RE: SDLC Best Practices

An out-of-office message containing personal information or a comment that violates community policies was deleted by the administrator.
Charles171Lively at 1/17/2015 12:19:46 PM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

An out-of-office message containing personal information or a comment that violates community policies was deleted by the administrator.
Elshad929Lively at 1/17/2015 12:19:47 PM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

Hi Micheal,

I am sure a search on the net will give you many resources. However, I would look at the following points and build up my own SDLC:

1. Requirements for the financial accounting software (what do you want this software to deliver)
2. Look for enterprise packages that are available in the market (or do you want to build your own?)
3. perform a vendor assessment on the shortlisted vendors.
4. Have a contract drawn up for the identified vendor. This contract should contact at the minimum:
        a. Service Level Agreements
        b. Security requirements
        c. Warranty 
        d. arrangements, if the vendor goes out of service
        e. legal requirements
        f. area of jurisdiction
        g. penalties
        h. maintenance arrangements
5. have the vendor implementr the solution / implement inhouse
6. perform a thorough testing

Trust this helps! Happy to discuss further.
Shruti KulkarniEnergizer at 1/19/2015 6:19:10 AM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

Hello Michael,

When it comes to deciding which SDLC to choose from, general thumb rules to remember are:
  • Whether explicit requirements are already known (preferably before the start of the development work)?
  • Whether level of interaction with the business/end users will be relatively low through out the project?
  • Whether the dedicated resources (man, money, material) would be allocated for the project (preferably from the beginning itself)?
  • Whether risk of failure in the delivery or implementation of the end output is relatively low? 
  • Whether the costs for dedicated resources are relatively low, throughout the project?

If answers for most of the above questions is yes, then it would be better to follow Waterfall SDLC, otherwise if most of the answers are no, Agile is a better option. 

Hope this helps ...
Rohit BanerjeeInfluential at 2/16/2015 12:52:59 AM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

Hi Michael,

Personally I have found the following ISACA assurance framework as a comprehensive and robust document that provides some good real-world practices and guidelines.

Systems Development and Project Management Audit/Assurance Program 


It can be found at:
http://www.isaca.org/Knowledge-Center/Research/ResearchDeliverables/Pages/Systems-Development-and-Project-Management-Audit-Assurance-Program.aspx

renmedincLively at 3/30/2015 10:07:50 AM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

Hi Michael,

Personally I have found the following ISACA assurance framework as a comprehensive and robust document that provides some good real-world practices and guidelines.

Systems Development and Project Management Audit/Assurance Program 


It can be found at:
http://www.isaca.org/Knowledge-Center/Research/ResearchDeliverables/Pages/Systems-Development-and-Project-Management-Audit-Assurance-Program.aspx

renmedincLively at 3/30/2015 10:07:50 AM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

Hello Michael,

When it comes to deciding which SDLC to choose from, general thumb rules to remember are:
  • Whether explicit requirements are already known (preferably before the start of the development work)?
  • Whether level of interaction with the business/end users will be relatively low through out the project?
  • Whether the dedicated resources (man, money, material) would be allocated for the project (preferably from the beginning itself)?
  • Whether risk of failure in the delivery or implementation of the end output is relatively low? 
  • Whether the costs for dedicated resources are relatively low, throughout the project?

If answers for most of the above questions is yes, then it would be better to follow Waterfall SDLC, otherwise if most of the answers are no, Agile is a better option. 

Hope this helps ...
Rohit BanerjeeInfluential at 2/16/2015 12:52:59 AM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

Hi Micheal,

I am sure a search on the net will give you many resources. However, I would look at the following points and build up my own SDLC:

1. Requirements for the financial accounting software (what do you want this software to deliver)
2. Look for enterprise packages that are available in the market (or do you want to build your own?)
3. perform a vendor assessment on the shortlisted vendors.
4. Have a contract drawn up for the identified vendor. This contract should contact at the minimum:
        a. Service Level Agreements
        b. Security requirements
        c. Warranty 
        d. arrangements, if the vendor goes out of service
        e. legal requirements
        f. area of jurisdiction
        g. penalties
        h. maintenance arrangements
5. have the vendor implementr the solution / implement inhouse
6. perform a thorough testing

Trust this helps! Happy to discuss further.
Shruti KulkarniEnergizer at 1/19/2015 6:19:10 AM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

An out-of-office message containing personal information or a comment that violates community policies was deleted by the administrator.
Elshad929Lively at 1/17/2015 12:19:47 PM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

An out-of-office message containing personal information or a comment that violates community policies was deleted by the administrator.
Charles171Lively at 1/17/2015 12:19:46 PM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

An out-of-office message containing personal information or a comment that violates community policies was deleted by the administrator.
Charles171Lively at 1/17/2015 12:19:46 PM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

An out-of-office message containing personal information or a comment that violates community policies was deleted by the administrator.
Elshad929Lively at 1/17/2015 12:19:47 PM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

Hi Micheal,

I am sure a search on the net will give you many resources. However, I would look at the following points and build up my own SDLC:

1. Requirements for the financial accounting software (what do you want this software to deliver)
2. Look for enterprise packages that are available in the market (or do you want to build your own?)
3. perform a vendor assessment on the shortlisted vendors.
4. Have a contract drawn up for the identified vendor. This contract should contact at the minimum:
        a. Service Level Agreements
        b. Security requirements
        c. Warranty 
        d. arrangements, if the vendor goes out of service
        e. legal requirements
        f. area of jurisdiction
        g. penalties
        h. maintenance arrangements
5. have the vendor implementr the solution / implement inhouse
6. perform a thorough testing

Trust this helps! Happy to discuss further.
Shruti KulkarniEnergizer at 1/19/2015 6:19:10 AM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

Hello Michael,

When it comes to deciding which SDLC to choose from, general thumb rules to remember are:
  • Whether explicit requirements are already known (preferably before the start of the development work)?
  • Whether level of interaction with the business/end users will be relatively low through out the project?
  • Whether the dedicated resources (man, money, material) would be allocated for the project (preferably from the beginning itself)?
  • Whether risk of failure in the delivery or implementation of the end output is relatively low? 
  • Whether the costs for dedicated resources are relatively low, throughout the project?

If answers for most of the above questions is yes, then it would be better to follow Waterfall SDLC, otherwise if most of the answers are no, Agile is a better option. 

Hope this helps ...
Rohit BanerjeeInfluential at 2/16/2015 12:52:59 AM Quote
You must sign in to rate content.
(Unrated)

RE: SDLC Best Practices

Hi Michael,

Personally I have found the following ISACA assurance framework as a comprehensive and robust document that provides some good real-world practices and guidelines.

Systems Development and Project Management Audit/Assurance Program 


It can be found at:
http://www.isaca.org/Knowledge-Center/Research/ResearchDeliverables/Pages/Systems-Development-and-Project-Management-Audit-Assurance-Program.aspx

renmedincLively at 3/30/2015 10:07:50 AM Quote
You must sign in to rate content.
(Unrated)

Leave a Comment

* required

You must login to leave a comment.