Talk:Software engineering

Article Checklist for "Software engineering"

Workgroup category or categories	Computers Workgroup [Editors asked to check categories]
Article status	Developing article: beyond a stub, but incomplete
Underlinked article?	No
Basic cleanup done?	Yes
Checklist last edited by	--Mark Jones 19:50, 21 October 2007 (CDT)

To learn how to fill out this checklist, please see CZ:The Article Checklist.

---

Rewrite 21st October 2007

I rewrote the article to focus more specifically on software engineering and moved some of the previous content into stubs for other articles. I hope some of you like it. Please discuss how the article can be improved.

I'd love to see this article get approved status soon as it is a major subject within the Computers workgroup category. Is it ready now? Let's get things moving in that direction. --Mark Jones 19:50, 21 October 2007 (CDT)

SE is a complex field, I'm not sure if this article does it justice.

I'm a software engineering student, and it's a huge field. I've glanced through the article between classes and I plan to read it soon, and it seems solid. To be honest, I think it might be hard to write one entry that will please everyone, so I think there is a need to have a lot of related pages discussing the topics that can only be summarized in this article.—The preceding unsigned comment was added by Thomas Owens (talk • contribs) 07:58, 22 October 2007 (UTC)

lacking parts

It seems early important steps in SW engineering are lacking methods like Structured Programming, Predicate Logics, System Development Management are not even named while they have played an important role in the development of methods to increase efficiency and maintenance of software development.—The preceding unsigned comment was added by Robert Tito (talk • contribs) 08:12, 22 October 2007 (UTC)

I, too, think this article is lacking in parts. Like any form of engineering, software engineering is based, in part, on scientific principles; those should be discussed, at least briefly, in this article. There also seems to be apparently contradictory (and poorly cited) bits on the origin of the term "software engineering". There should also be discussion of several different arena for software engineering, such as shrink-wrapped commercial software, enterprise software, embedded software, and (forgetting the correct name) the high-reliability software required for avionics and medical devices. Anthony Argyriou 11:47, 22 October 2007 (CDT)

Most of the topics mentioned above would be more suited to subtopics and linked from the main article in some way. Also, Anthony, can you be more specific about which parts are contradictory and poorly cited so that I, or someone else, can fix it? Many thanks. --Mark Jones 14:34, 22 October 2007 (CDT)

Requires the major models that comprise Software Engineering

This is a good start. The above comments might be helped with including the major models and frameworks commonly used. These may lay the foundation for a better understanding of the field. It might also help to have some of its leading minds listed. —The preceding unsigned comment was added by Andrew M. Colarik (talk • contribs) 19:37, 22 October 2007 (UTC)

Thanks. I think things like models and frameworks are best mentioned (and linked to as subtopics) to the not-yet-created article Software development process which I have linked to in the main Software engineering article.

Articles not meant to be exhaustive

Thanks for the feedback. In answer to some of the above comments, remember, the article is meant to provide an introductory overview of the subject to a layperson not exhaustive coverage (which would require an entire book!). The idea is to provide links to subtopics so people can drill down to the finer details if they so wish. It was decided fairly early on that this was going to be the best approach for writing articles for Citizendium, not try to cram all the details into one article (as is the case in many Wikipedia articles). Many of the lacks cited above can be solved by writing sub-articles and adding links to this article. Remember, some topics will be subtopics of subtopics so they don't all need to go in the software engineering article. --Mark Jones 14:25, 22 October 2007 (CDT)

For example, this article already links to Software development process which is a subtopic of the article. This subtopic article should describe an overview of process models and link to specific models as subtopics. These models should be described fully on their own pages. This way the lay-reader who has only a fleeting interest in Software Engineering is not overwhelmed by too much detail (that they possibly won't understand or care about) in main article but can drill down to specific topics he or she is interested in. --Mark Jones 15:03, 22 October 2007 (CDT)

I completely agree with the intention not to overdo and be exhaustive BUT since this is the history of the topic it needs placing things in historic perspective. It makes no sense to give attention to outdated methodologies like SDM but they need being mentioned as well as why they were intensively used. The more modern methodologies (be it UML or OO methodologies) do need their own subpages but the old things, I don't think so. Maybe for the interested but not for the lay man taking a peek to see how and what this engineering is all about. Robert Tito |  Talk