Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 1 year ago.
Improve this question
I have two modules of an app. one is parent app and another is child app. should I create two different class diagrams for both apps or should there only be one diagram?
This is entirely up to you to decide. Some thoughts that may guide you:
If the classes or components of these both classes deal with parts of the same domain (for example, one app is maintaining a catalogue, and the other allows to purchase catalogue items), you may consider one model.
If anyway you consider your apps two be just two faces of the same system, you should consider one model.
If the apps are two different things and only share some "modules", components, or classes (in a library), you may consider two or three models. THe package of the common part might then be imported into the model of the apps.
One model does not mean one diagram: in fact several diagrams may show the same model under different viewpoints. So you might very well use several diagrams, each focusing on some elements of one of the app.
You could even have one diagram to show the main classes of both apps and several other diagrams showing some of those classes as well as more detailed classes. The key is to keep each diagram of one model sufficiently simple to be easily understood.
Whatever the situation, avoid a huge mega-diagram showing everything with 50 classes: nobody except you would be able to absorb such a complexity.
If you're confused regarding the difference between modeling models and drawing diagrams, you may have a look at this question
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 years ago.
Improve this question
I googled the above question in many forms and I could not find any comprehensible answer. Can someone give a real life example that explains the difference between a business process and a workflow ? and how each one is connected to activities.
This diagram was supposed to help but to be honest, it confused me even more.
Questions like this aren't the core purpose of Stack Overflow, so probably you'll get a few flags. But I'll try to give a short answer.
Like many other notions in computing, these two terms, business process and workflow, aren't precisely defined, at least not in a way that is generally understood and accepted. So each author, tool vendor, and the like, use them at their pleasure. For most practical cases, they are interchangeable. BPMN, for example, has "business process" in its name, but many "workflow" engines do nothing else than implement BPMN.
A diagram like the one you got isn't meaningful without a clear explanation of the meaning of its constructs. That's the duty of its author and can't be done by you or me without knowing his intentions.
If anything, the term "workflow" could be more specific than "business process". The workflow means the concrete sequence of actions, like "customer fills order, then vendor calculates delivery data, then warehouse personell fetches products,...". Business process can, depending on the context, also be used for more abstract ideas, like "product design, customer acquisition, order processing" that are not directly related in the everyday work organization.
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 7 years ago.
Improve this question
I'm making a class diagram for a media library, like iTunes or Windows Media Player. My library contains audio, video and images.
I'm fairly new to this, so I'm not sure if I'm heading in the right direction. This is what I got so far:
I feel like there should be a few more classes. Does anyone have some tips/suggestions on how to improve/expand this class diagram?
EDIT!
I've tried to make the playlists a bit more clearer. I've also added an interface:
It seems fine to me in the main lines:
The Media specialization seems correct
The Person specialization seems correct
The Directs and Composes relationships seem right
Nothing seems wrong here. But the Playlist composition is however not very clear. I have no obvious alternative, but here is the point...
How it is introduced, your playlist might be composed by images, videos, audio records. The question is the relationship between the compositions.
If you wish a playlist composed by image OR videos OR audio records non-exclusively, the playlist should be composed by medias in general.
If you wish a playlist composed by image OR videos OR audio records exclusively, things become quite subtle. In your representation this is not obvious at all. At least a note should be welcome in order to specify the exclusive composition relationship. A solution would be to specialize the playlists: the specialized version would be instantiated on the insertion of the first element. This is up to what you really want to show. In any case, an explanation note would be very useful.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I'm making a typo3 site and need to have a database which consists two tables: manufacturer and category. a manufacturer can have multiple categories and, besides company name and link, has a few images which are displayed in a gallery.
In the frontend, there are two differnet pages which list the categories. A click on a category leads to a page where the manufacturers of this category are listed. The categories and manufacturers need to editable in the backend.
I have thought about creating classical typo3 content elements, but this has the disadvantage that there is no database structure in the backend and therefore it would be required to create two of the same content elements for different pages.
Clearly, having a database is the better method. My knowledge of typo3 is not the best and my question is: what would be the best approach to implement such a database? Is there an extension for such cases or do i need to create an extension using extbase? And, in the latter case, how difficult would it be to create an editor for the backend in which the content can be entered into the database and the images can be uploaded.
I did hours of research but wasn't able to figure out what the best approach would be. I'm not looking for some ready-made solutions (except for the case that there is one for this specific problem) but for some hints which point me into the right direction. I have no problem with learning how to create an extension; i just would like to know if it's worth the time.
Use Extension Builder to create new extension with all elements you need: additional tables, fields, FE plugins, custom CE's, even BE modules just with click'-click' solution.
It just matter of several minutes to build models properly... in such case it generates valid TCA, so you've got backend ready to use out-of-the-box. For FE you'll need to put some additional effort.
Summarizing, yes it's worth the time.
And sorry... I must mention: TYPO3 (not typo3) is written with uppercase, always
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 9 years ago.
Improve this question
I wish to make an iOS application that includes a document library, log/journal, forums, possible randomized quotes ?and coaching tools?, and have built applications of that size in other contexts but this is my first iOS application.
Right now I'm working through http://www.raywenderlich.com/1797/how-to-create-a-simple-iphone-app-tutorial-part-1 , and I'd welcome comments on other tutorials, but I wanted to ask: does it work to work out the logical gears of an application before developing the graphic design? I would like to have somewhere between a Dirtylicious and Nature look, but my natural bent (no pun intended) is to get most the gears working and then defer most of the design work until after the gears. I expect they should not be completely separated, and there are cases where you apply the design and then realized that what the gears are doing only looked good on paper, but I wanted to do a sanity check on whether it makes to look up tutorials appropriate to a document library, a log/journal, forums, etc. and get them to work together first, and then skin it.
TIA,
It is recommended that you follow the MVC pattern, which strives for separation between layers.
http://developer.apple.com/library/ios/#documentation/general/conceptual/devpedia-cocoacore/MVC.html
Xcode helps you implementing that pattern.
I think you should try to put in "paper" everything you want to do, before doing any actual coding, check how many views you are gonna have, what you need, the flow between views, try to diagram everything, that will save you a lot of pain later. You don't have to be so specific about the GUI at this stage, you only need to know what kind of visuals you need in the views, (buttons, labels, etc...)
And yes, I think you're safe doing the Model first.
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
Why adopt the UP process over others? What are the relative advantages? I know that it is closely coupled with UML but clearly this cannot be the only advantage? Why choose this approach over others?
I think it really depends against what process/methodology you compare. Without details, only general characteristics of UP can be mentioned.
It is iterative incremental methodology with well described roles and activities, using modeling techniques in object oriented analysis and design. It is vertically (time) divided in phases and those in iterations and horizontally into groups of activities concerning different aspects of software development, such as requirements, analysis, design, testing deployment etc...
Although we are not practitioners of the full UP processes, we use it frequently to see what type of products we need and which roles will have the responsibility to perform the activities for that product. We like it, because it details the various aspects from design until the deployment phase and comes with various templates, guidelines and processes which help out in the development life-cycle.
Take a look at : http://epf.eclipse.org/wikis/openup/
As we are a team where members can play different roles depending the projects, we simply navigate to the role, and check what products are needed for the project at hand. Depending the weight/complexity of the project we will choose the products that will help us in our daily duties. UML is an asset which we highly depend upon and comes as a benefit within OpenUP (or other UP incarnations).
I am certified in RUP and a Scrum Master. Most teams find that no process "off the shelf" is a perfect fit. That being said, the Unified Process focuses on driving risk out of a project early. However, I have seen many implementations where UP introduces a level of risk simply by being overly complex. Depending on the nature of the project, organizational structure, and other factors such as compliance and scale, UP offers a set of practices that can be easily tailored.