I’ve been reading about the sdlc activites and I’d like to compose a
short list of things to do when starting a new app. I just wanted to ask
in general what you guys are using to design a new app. I guess it
applies “to each his own” when it comes to personal preferences, but
still…
I’d like to come up with a concise template for each iteration in sdlc
to minimize the documentation but covering all the bases.
On Mon, Sep 23, 2013 at 11:23 AM, Sebastjan H. [email protected]
wrote:
I’ve been reading about the sdlc activites and I’d like to compose a
short list of things to do when starting a new app. I just wanted to ask
in general what you guys are using to design a new app. I guess it
applies “to each his own” when it comes to personal preferences, but
still…
I’d like to come up with a concise template for each iteration in sdlc
to minimize the documentation but covering all the bases.
I mean an app or a computer program of a scope that would require
something like that. Obviously a small script would not fall in that
category, but something more complex like a project managament system.
On Mon, Sep 23, 2013 at 1:55 PM, Sebastjan H. [email protected]
wrote:
What do you mean by “app”?
I mean an app
I hope you do notice that this is self referential.
or a computer program of a scope that would require
something like that. Obviously a small script would not fall in that
category, but something more complex like a project managament system.
OK, so you are talking about applications written in Ruby. I had
asked because from your original posting it was not entirely clear to
me that you do not mean smartphone apps.
Meanwhile, I found the something similar to what I had in mind here:
Execution Verification Tests (Which directly tie to each of the types
of the General Test Types, listed below…)
General Testing
All Unit & Module Tests
All Systems Integration Tests
All Performance Tests
Most User Acceptance Tests
Most Security Penetration Tests
Disaster Recovery Tests
The automation of the above is tied directly into our Continuous Build &
Integration Framework (CBIF) that pretty much runs on demand (any time a
change is implemented in an environment).
We layer an Agile-like approach over the SDLC, where we run things
through the SDLC in small groups of changes so we can move things as far
and as fast through the pipeline as possible. And, we use Project Plans
that account for all work in every SDLC Phase. Since the Phase layout
is repeatable, the Project Plans make for highly repeatable templates
that can be reused for most Projects, minimizing having to recreate new
plans from scratch.
On Mon, Sep 23, 2013 at 1:55 PM, Sebastjan H. [email protected]
wrote:
What do you mean by “app”?
I mean an app
I hope you do notice that this is self referential.
I’ve only just realized why “app” was confusing, I’m sorry for that
or a computer program of a scope that would require
something like that. Obviously a small script would not fall in that
category, but something more complex like a project managament system.
OK, so you are talking about applications written in Ruby. I had
asked because from your original posting it was not entirely clear to
me that you do not mean smartphone apps.
Meanwhile, I found the something similar to what I had in mind here: