Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Object Oriented Analysis & Design
Previous Previous
 
Next Next
New Post 9/10/2014 2:17 PM
Unresolved
User is offline Mhd_JN
2 posts
No Ranking


Object Oriented Analysis & Design 

Good evening every body

I am very proud to be a member of this Community

I hope to introduce something here.

I wonder if here issues regarding OBJECT ORIENTED ANALYSIS & DESIGN ?

Many thanks

 1 Reports
New Post 9/14/2014 1:41 PM
User is offline Adrian M.
724 posts
3rd Level Poster




Re: Object Oriented Analysis & Design 

Welcome to the ModernAnalyst.com community for Business Analysts!

I'm not sure I understand your question.  CAn you please restate?

Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 9/18/2014 3:00 PM
User is offline Mhd_JN
2 posts
No Ranking


Re: Object Oriented Analysis & Design 

Thanks for your care.

As you know, when we build ERP system (Or any computer based system), we start by sitting with user to collect their requirements, and then document them as Use case models. After that you start analysis by making static analysis, then dynamic analysis.

The design phase starts by making design documents.

Then we start coding.

Actually, there are some approaches for Object Oriented analysis & design (XP, RUP, Ripple  ...etc.).

So, I am asking if there is a place here for discussing these Issues?

 

 
New Post 9/19/2014 3:21 AM
User is offline Kimbo
438 posts
5th Level Poster


Re: Object Oriented Analysis & Design 

Sure discuss away. Disagree with just about everything you've said so far but the beauty of this site is that everyone is equally entitled to a voice (just ask Tony M!)

Perhaps you could explain what static and dynamic analysis are and the difference between them.

Kimbo

 
New Post 12/3/2015 1:35 AM
User is offline FrancisClarke
2 posts
No Ranking


Re: Object Oriented Analysis & Design 
Modified By Chris Adams  on 12/3/2015 2:48:38 PM)

Hi,

I am new here but liked the discussion, yesterday I was reading online about the same and sharing it with you too.

Dynamic analysis is analytical testing in that the intention is to examine the test item rather than exercise it. It is white box testing in that we examine internal rather than external behavior. Yet the code under test must be executed, and that is done by running the same black box tests used for dynamic testing.

Static code analysis provides information to help predict what may happen when code is integrated and executed. It detects defects based on what the tool considers a defect (typically, this can be customized to suit your preferences and priorities). However, it cannot tell you when the system under test or in production does NOT do what it is expected to do—or does something that nobody expected it would do.

Dynamic analysis is analytical testing in that the intention is to examine the test item rather than exercise it. It is white box testing in that we examine internal rather than external behavior. Yet the code under test must be executed, and that is done by running the same black box tests used for dynamic testing.

Hope it is useful for you too.:)

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Object Oriented Analysis & Design

Community Blog - Latest Posts

Ekaterina Barabash
Ekaterina Barabash
I address my thoughts to those who are in IT management for whom the terms such as quality of project implementation development and profitability indicators of the company are important.  And it is also addressed to business analysts whose daily routine is the process of communication with Customer. A little about myself first. The last 8...
1 Responses
Dan Tasker
Dan Tasker
I have long been a believer in the saying “Context is everything.” As a business analyst dealing with business users, understanding the context of the topic of discussion is essential. In thinking about what constitutes quality requirements it occurred to me that there are a number of additional contexts that play a role. Examples inclu...
2 Responses
Alexey Kiselev
Alexey Kiselev
We are writing User Stories to fix the scope and describe - what our application should do when implemented.User Stories are great, because the are: Short, Defining Roles, A great connection of the requirement itself and a business need. User Story declared as a high level definition of the requirement, but it could be used to s...
0 Responses




Latest Articles

Adding Value as an Agile Business Analyst
Dec 09, 2018
0 Comments
As more organizations move toward agility, development and project management teams still struggling to define a common language and standard regardin...
Featured Digital Library Resources 
Copyright 2006-2018 by Modern Analyst Media LLC