Presentation about our company and what we do (analysis of software projects). Before starting to develop software, it is important to know WHAT should be programmed by performing an analysis.
What do you learn?
1. Before starting to develop, take sufficient time to think out suitable solutions.
2. Create structured documention, in a clear and understandable way, to inform all stakeholders.
3. The analyst is a key player in a project team.
1. Specialised analysts, or do you let your
developers rectify your software?
Company presentation
I used this presentation to talk for about 20
minutes about our company and what we do.
It is not the aim to go in detail about analysis, but
to give a global view.
The semi-transparant sticky notes denote what is
said during the presentation.
2. 18/04/2013 Brain Cell IT bvba 2
Hello,
I am Brian Kegels.
I am consultant for 12 years including 6 years as a
developer in Microsoft environments (.NET, C#, SQL
Server). I worked for Capgemini at clients as
Exxon, government, Manpower and others.
Currently I work as a consultant analyst and I am
founder, owner and manager of my company where I
have all-round tasks (sales, HR, PR, administration and
so on).
In 2006 Brain Cell IT started with consultancy activities.
This means we fulfill assignments for our customers.
These assignments consist of analysis tasks for
software projects, mainly functional analysis, but
sometimes also business analysis based on the
experience we built up.
Our customers are big companies and multinationals in
different sectors, mainly Banking and payroll
companies.
References: De post (Belgian post), BNP Paribas Fortis,
JNJ, SD Worx, Acerta.
3. 18/04/2013 Brain Cell IT bvba 3
Idea
Wishlist
Plan
Build
Test
Delivery
2 badkamers
Zwembad
Open haar
Wijnkelder
Geheime gang
Grote slaapkamer
Bioscoop
2. He has a few
wishes. Requirements
he absolutely wants,
and some he does not
want.
Before programming software, it is important to know, WHAT
should be programmed. Analysis is as important as (maybe
more important than) programming or testing. But where in
the software development life cylce is it situated?
Let’s make a comparison with building a house.
1. Suppose that Bob
has the idea to build
a villa in Antwerp.
3. The architect is in
charge for working out
a detailed plan, a
blueprint of the project.
5. Finally the keys to
the villa are
delivered to Bob.
4. The villa is built by
the builders and
tested (on loss of
warmth for example).
4. 18/04/2013 Brain Cell IT bvba 4
Idea
Wishlist
Plan
Build
Test
Delivery
2 badkamers
Zwembad
Open haar
Wijnkelder
Geheime gang
Grote slaapkamer
Bioscoop
1. Idea: check
savings account
online
2. Requirements:
secure, online, at least
20 last transations, ...
(requirements
gathering, business
analysis)
3. Plan: list the reactions
of the system triggered
by the actions of the
user; design schemes, ...
(functional analysis)
4. Build and test: by
the builders
(programmers) and
testers.
5. Delivery:
Configuraton, roll
out, ...
If we compare with an IT project, let’s say for a bank:
5. The analyst is the architect of software.
18/04/2013 Brain Cell IT bvba 5
The architect designs and sketches a plan to be build by the
“builders”.
Like an architect the analyst:
•Sketches and designs screens, flows, diagrams
•Writes rules, use case documents, plans
The analyst:
•Studies specific business requirements of certain processes.
•Translates requirements to technical perspective, though
clear to read for all stakeholders.
•Documents in a structered way, easy and clear.
6. 18/04/2013 Brain Cell IT bvba 6
Interview
Workshops
Inform
stakeholders
Sketch screen
designs
Initial tests
Search for creative
solutions
Study specific
topics
Document
Discuss
Coaching
Defend customer
needs
Because of the multitude of
activities and responsabilities
the analyst is a key person in
project.
7. An analysis is as a contract.
18/04/2013 Brain Cell IT bvba 7
The analysis is used to:
•Define the requirements of the different parties
•Describe the procedures
•State what is in scope or what is out of scope
The analysis must clearly specify what must be
developed and what must not be. It must be
understandable by all stakeholders, programmable by
developers, testable by testers and so on.
8. 18/04/2013 Brain Cell IT bvba 8
Some extracts from analyses:
A class diagram, a use case diagram
and a use case description.
10. Where do we fit?
18/04/2013 Brain Cell IT bvba 10
How?
Tools?
Environments?
Customers?
Basically we are technology
independent, but we take into
account technical limitations.
Mostly we use UML and use case
descriptions.
Word, Paint?
Professional tools such as Sparx
Enterprise Architect, Rational
Rose, MS Visio, ...
Microsoft .NET or Java
Windows or Web
Big or multinational enterprises,
mostly financial institutions or
payroll companies
11. 18/04/2013 Brain Cell IT bvba 11
Our
philosophy
Trust
Familiarity
Ethics
Quality
Involvement
Brain Cell IT believes a humane and ethical
manner of working is important for
delivering high quality of work.
We have a flat organization, we aim for
mutual respect, trust, personal contact and
personal coaching.
We KNOW our collaborators.
12. 1. Before starting to develop, take
sufficient time to think out suitable
solutions
2. Create stuctured documentation to
inform all stakeholders
3. The analyst is a key player in a project
team
What did we learn today?
18/04/2013 Brain Cell IT bvba 12
13. Up to you now...
• Sander Hoogendoorn
www.sanderhoogendoorn.com
• LinkedIn Groups:
– UML
– UML Lovers
– Use Case Professionals
• Blogs:
http://caminao.wordpress.com/overview
http://briankegels.wordpress.com
• Just use it!
18/04/2013 Brain Cell IT bvba 13
Sander is recognized in the
Netherlands and Belgium for Agile
development and UML in the full
spectrum. He wrote this book
covering all diagrams in UML (also
rather technical). It is easy to read
and contains many practical
examples.
<- my blog !
15. Brian Kegels
Manager Brain Cell IT
brian.kegels@braincell-it.com
www.braincell-it.com
briankegels.wordpress.com
My details
18/04/2013 Brain Cell IT bvba 15