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 6 years ago.
Improve this question
I'm looking for clarification -
The terms 'structured programming' and 'structured development approach' refer to different things. Is this correct?
My understanding is that 'structured programming' is programming which is clear and well set out, using subroutines and modules etc. to keep 'structure' in software. This is different to the 'structured software development approach' which refers to the methodology of completing the stages of development (defining the problem, planning, creating, testing and maintenance) sequentially and not starting one until the previous is finished.
I'm a student and need to have these terms clear. Am I on the right track? Are there any important details I'm missing?
Yes, you are on the right track, these are different things.
Both of these terms are very broad. All programming paradigms that have been in use during the last 50 years (procedural, object oriented, functional etc.) are structured. And I would also say that every development methodology (waterfall, v model, agile etc.) is also structured in some way. Of course there are different grades.
Related
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 last month.
Improve this question
People say practicing and keeping up to date with the latest technologies makes you a good developer, but what are some lesser known practices you all can suggest for someone currently doing a Bachelor's degree in Software Engineering and wants to stand out in their Master's application abroad?
I've started writing technical articles on Medium, finding open source contributions (which I rarely find for beginner level and any suggestions would be appreciated) and doing coding challenges online. Is there anything else I should be focusing on?
you've got plenty of time. keep learning technologies you're interested in, do projects and develop your skills along the way I'd say. Participate in competitions if you can. Open source contribution is a pretty good step
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 5 years ago.
Improve this question
I've been developing a small database for my summer internship and I need to write a manual/documentation for it aimed at both users and developers for future use. Thing is...I have no idea where to start or what information to include. Many people I work with have no idea what databases can do so I need to keep it as simple as possible. The database is implemented in Access and I experimented with the database documenter but I think that is overkill. Is there some kind of documentation standard that I can follow or anything of that nature?
As a starter for ten, I'd have thought that the user documentation should be task orientated.
(i.e: How to achieve 'X'.)
In terms of the developer documentation, defining the meaning of any non-obvious fields in your schemas, how they're used and the relationships between different tables, etc. would be a good start. (I'm presuming your VBA code is well commented, etc.) You may also want to examine the existing "Documenting Visual Basic with Doxygen" question/answer.
Just straightforward english if you are explaining a process.
If you have a series of Macros do a document highlighting to code used in each macro and the order it should be employed. This could aid someone down the line if they are trying to automate the process.
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 am involved in a project which is meant to eventually become open-source and have a code contributor community. Is there any "right" way of doing this and what should/can I expect?
Thanks
There's a pretty good book on this topic, Producing Open Source Software by Karl Fogel, which is available for free online or in dead tree form if you prefer to read it that way. It would be hard to expand much on it in a single answer. Every project will, of course, be different, so I'd recommend reading that book, and then asking more specific questions about your particular project; answers will depend on the language and platform you use, how active an open source community there already is in your area, what your business model is, and many other factors.
I would recommand using Github or Google Project Hosting (subversion/mercurial), and of course use social media network to promote the project helps too.
You can start something like this - http://wxwidgets.org/develop/
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I'd like to know the difference between Software Development Process and Software Development Methodology if there is any.
A process is only a component of a methodology. A methodology has:
A process aspect: what tasks are to be carried out?
A product aspect: what things are to be used and/or created?
A people aspect: what people and teams are going to do all this?
A time aspect: how does all this get organised in time?
A modelling aspect: what modelling units (language) are used to capture all this?
This is a simplified interpretation of the more formal definitions that you can find in ISO/IEC 24744 Software Engineering - Metamodel for Development Methodologies.
Still, the terms "method", "methodology" and "process" are used by different people with different meanings. After 20 years working in this field, I think that trying to agree on a standard use is futile. :-)
It's the same as the difference between process and methodology in any other discipline. I think of the processes as the implementation of the methodology.
The methodology is more a general mindset which sets basic parameters. A process is a concrete manifestation within the given borders of the methodology. You can think of agile as methodology and Scrum as concrete implementation.
Sometimes it's hard to distinguish between the two. As rule of thumb: If you can immediately start to work with it, it's probably a process. A methodology requires more adaptation .
A more wide term would be Software Development Philosophies.
http://en.wikipedia.org/wiki/List_of_software_development_philosophies
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 8 years ago.
Improve this question
Upon reading a blog post about a minimalist story-generating python program, I was asking myself - and you - which are the most successful attempts at such programs. I remember seeing something using generating grammars, for instance. And which are the best attempts that, like this one, are extremely compact, either self-contained or able to read, say, the Web or an independent textual corpus (but not simply a file with a large number of story chunks)?
Search for Talespin for some famous ground breaking work. (Example: Micro-Talespin in Common Lisp by Warren Sack.)
I actually like Turner's "Minstrel: A Computer Model of Creativity and Storytelling" better :
ftp://ftp.cs.ucla.edu/tech-report/1992-reports/920057.pdf
Talespin is, in my opinion, blind in it's algorithm to everything but planning. So the author goals are given very little consideration (if at all). Minstrel is better that way.