Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have come across tools like visualparadigm demo which could automatically generate code from the class diagram which is modelled in UML. Since I have no industry experience, I am curious to know whether this is the way companies start working on their projects after the system is modelled in UML. since the skeleton of the classes needed is automatically generated, I assume it is a good way to save time. If this is not the way, then why is it so?
Also Can you provide me some other tools which can automatically generate code from UML class diagrams (prefer opensource).
Are there OOP software projects which do not get started with the class diagrams, so that this method can be of no use?
Most of UML are able to generate code from UML class diagram you just have to google it and you will find them.
Concerning the way companies start working, I guess it depends of the companies but from my experience companies try to avoid useless work.
If they spend some time on modeling it is because they can use it for something for example code generation, documentation, or just because its a client request. If companies do not find any interest in modelling they simply do not use it I guess that alot of OOP do not start with models.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 months ago.
Improve this question
Describe the system architecture in the last 3 projects you worked on. In this case I don't know what system architecture they mean?
Which components listed above have you been working on?
What frameworks are used during the development of these components?"
From a interviewer perspective, they are trying to assess candidates knowledge of overall system they worked up on.
Describing system architecture will help interviewer to know whether candidate knows the big picture of the systems they were part of. The answer could be by explaining the logical architecture(functional view) of application or a component architecture(tech view) depending on context. For a person who is oriented more on infrastructure side, this could be still a bit different, but rarely the case.
Question "on which component have you worked" primarily is intended to understand what exactly was candidates role in project. Explanation on how the component was designed, what technologies are used etc could be answered.
"Frameworks used" would probably tell the interviewer whether candidate was into decision making roles for design or at least can evaluate what is best fit for the need and what is not. Mentioning the frameworks(or libraries or plugins based on tech landscape) used and how that well suit the needs would be a good answer.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I want to know what kind of diagrams I should use in each step of a project lifestyle, for example in the first step I should do the use case diagram, but what diagrams should I do after this step, for example what diagrams I should use during the analyse of the project, the design, etc.
First of all you should decide which process model you want to use. Let it be Waterfall (not recommended), V-Model, Scrum, Unified Process, Rational Unified Process, etc.
Then you can start talking about first, second step and so on, because the steps depend on the process model that you use.
These diagrams you're referring to are also called artifacts, and you should only use them, if you need them and if they create value (more understanding for example), you should not use them just to have done it (only if it's an academic/school project and you want to learn).
If you want to improve your knowledge in that certain area, there are several good books out there, e.g. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development by Larman.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I'm learning about UML diagram and sequence diagram at the moment in one of my courses for my CS degree, and I wonder that if this is something that is common to use for developers or if this is just one of many approaches to analyse the design of the system.
I'm so used to the Waterfall model and wondering if there would be any benefits for switching my mindset.
Maybe the answer is obvious, but still think it would be interesting to hear from people that are more experienced in the area.
My first advice is not to mix concepts:
UML = modeling language.
Useful to describe/visualize the design of a system.
Waterfall model = design process.
Useful to describe in a linear-sequential manner the life cycle of a system.
This is a very short and non-deep description but ilustrates your question about the specific case of sequence diagrams, so in a real case scenario you probably will end using both like this:
-Requirement/Analysis: during this phase you will start creating some of the first UML Use case diagrams for your system.
-System Design: during this phase (or even earlier) you will start creating UML Sequence diagrams, UML Component diagrams and so on.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
It's been a really long time since I worked with UML Diagrams.
I started working with UML Use Cases again, for a real world project. I would like to ask some questions.
How should I approach writing use cases?
I believe the tasks that leads to a "Major/Bigger" task should not be considered as use cases by themselves. Am I right?
Okay, what if I have a task like View tutorial and it has Comment on Tutorial, Favourite Tutorial, etc. Should these be separate use case, Extending View Tutorial? If yes, but, aren't they small features, why we should include them?
I'm mixing some stuff here, I hope someone could enlighten me .
Thanks!
Read Alistair Cockburn's Effective Use Cases book (see it on Amazon: 1). He does an excellent job of explaining practical use of use cases in a structured and effective way.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am taking a software development class right now and we are discussing agile methodologies. What are the most common agile methods? I need to look into several and discuss their strengths and weaknesses. Seems more useful to look into the most prominent methods.
Observations:
Scrum seems pretty popular (that is what my team used on two of my coops).
Extreme also seems to get quite a bit of buzz but I am not sure if that many people actually use it.
What does your company use and how do you like it? Does anyone use:
Agile Modeling
Agile unified process
DSDM
Essential Unified Process
Feature Driven Development
Open unified processes
Rational Unified Process
Are there other methodologies that I should investigate?
I've used SCRUM in personal projects with friends and schoolmates and my current employer uses a custom agile process that's very similar to SCRUM but with fewer meetings.
We have used Test Driven Development and Scrum.
I've been on some very successful teams which used Scrum very effectively. It really does help to keep everybody focused and constantly moving forward, and it discourages regressions.