Search
Search titles only
By:
Search titles only
By:
Log in
Register
Search
Search titles only
By:
Search titles only
By:
Menu
Install the app
Install
Forums
New posts
All threads
Latest threads
New posts
Trending threads
Trending
Search forums
What's new
New posts
New ads
New profile posts
Latest activity
Free Ads
Latest reviews
Search ads
Members
Current visitors
New profile posts
Search profile posts
Contact us
Latest ads
Pure VPN - Up to 27 Months
vgp
Updated:
Friday at 8:10 AM
එක පැකේජ් එකයි මාසෙටම Unlimited Internet. තාමත් DATA CARD දාන්න සල්ලි වියදම් කරනවද? අඩුම මිලට අපෙන්.
sayuru bandara
Updated:
Tuesday at 12:30 PM
Ad icon
ඉන්ටර්නෙට් එකෙන් හරියටම සල්ලි හොයන්න සහ Success වෙන්න කැමතිද? 🚀 (E-Money & Success Stories)
siri sumana
Updated:
May 30, 2026
Gemini AI PRO 18 months Offer
Hawaka
Updated:
May 27, 2026
Ad icon
koko account
DasunEranga
Updated:
May 27, 2026
Electronics
Vehicles
Property
Search
Reply to thread
Forums
General
ElaKiri Talk!
IT Help for a Beginner
Get the App
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Honda.putha" data-source="post: 28553655" data-attributes="member: 565644"><p>Here are the most important subjects for software engineering, with brief explanations:</p><p></p><p></p><p><strong>1.Object oriented analysis & design</strong>: For better maintainability, reusability and faster development, the most well accepted approach, shortly <a href="http://en.wikipedia.org/wiki/Object-oriented_analysis_and_design" target="_blank">OOAD</a> and its <a href="http://en.wikipedia.org/wiki/SOLID_%28object-oriented_design%29" target="_blank">SOLID</a> principals are very important for software engineering.</p><p></p><p><strong>2.Software quality factors</strong>: Software engineering depends on some very important <a href="http://en.wikipedia.org/wiki/Software_quality" target="_blank">quality factors</a>. Understanding and applying them is crucial.</p><p></p><p><strong>3.Data structures & algorithms</strong>: Basic <a href="http://en.wikipedia.org/wiki/List_of_data_structures" target="_blank">data structures</a> like array, list, stack, tree, map, set etc. and useful <a href="http://en.wikipedia.org/wiki/List_of_algorithms" target="_blank">algorithms</a> are vital for software development. Their logical structure should be known.</p><p></p><p><strong>4</strong>. <strong>Big-O notation: </strong><a href="http://en.wikipedia.org/wiki/Big_O_notation" target="_blank">Big-O notation</a> indicates the performance of an algorithm/code section. Understanding it is very important for comparing performances.</p><p></p><p><strong>5.UML notation</strong>: <a href="http://en.wikipedia.org/wiki/Unified_Modeling_Language" target="_blank">UML</a> is the universal and complete language for software design & analysis. If there is lack of UML in a development process, it feels there is no engineering.</p><p></p><p><strong>6.Software processes and metrics</strong>: Software enginnering is not a random process. It requires a high level of systematic and some numbers to monitor those techniques. So, <a href="http://en.wikipedia.org/wiki/Software_development_process" target="_blank">processes </a>and <a href="http://en.wikipedia.org/wiki/Software_metric" target="_blank">metrics</a> are essential.</p><p></p><p><strong>7.Design patterns</strong>: <a href="http://en.wikipedia.org/wiki/Software_design_pattern" target="_blank">Design patterns</a> are standard and most effective solutions for specific problems. If you don't want to reinvent the wheel, you should learn them.</p><p></p><p><strong>8.Operating systems basics</strong>: Learning <a href="http://en.wikipedia.org/wiki/Operating_system" target="_blank">OS</a> basics is very important because all applications runs on it. By learning it, we can have better vision, viewpoints and performance for our applications.</p><p></p><p><strong>9.Computer organization basics</strong>: All applications including OS requires a hardware for physical interaction. So, learning <a href="http://en.wikipedia.org/wiki/Microarchitecture" target="_blank">computer organization</a> basics is vital again for better vision, viewpoints and performance.</p><p></p><p><strong>10.Network basics</strong>: <a href="http://en.wikipedia.org/wiki/Computer_network" target="_blank">Network</a> is related with computer organization, OS and the whole information transfer process. In any case we will face it while software development. So, it is important to learn network basics.</p><p></p><p><strong>11.Requirement analysis</strong>: <a href="http://en.wikipedia.org/wiki/Requirements_analysis" target="_blank">Requirement analysis</a> is the starting point and one of the most important parts of software engineering. Performing it correctly and practically needs experience but it is very essential.</p><p></p><p><strong>12.Software testing</strong>: <a href="http://en.wikipedia.org/wiki/Software_testing" target="_blank">Testing</a> is another important part of software engineering. <a href="http://en.wikipedia.org/wiki/Unit_testing" target="_blank">Unit testing</a>, its <a href="http://richard.jp.leguen.ca/tutoring/soen343-f2010/tutorials/properties-of-good-unit-tests" target="_blank">best practices</a> and techniques like black box, white box, mocking, <a href="http://en.wikipedia.org/wiki/Test-driven_development" target="_blank">TDD</a>, integration testing etc. are subjects which must be known.</p><p></p><p><strong>13.Dependency management</strong>: Library (JAR, DLL etc.) management, and widely known tools (Maven, Ant, Ivy etc.) are essential for large projects. Otherwise, antipatterns like <a href="http://en.wikipedia.org/wiki/Java_Classloader#JAR_hell" target="_blank">Jar Hell</a> are inevitable.</p><p></p><p><strong>14.Continuous integration</strong>: <a href="http://en.wikipedia.org/wiki/Continuous_integration" target="_blank">Continuous integration</a> brings easiness and automaticity for testing large modules, components and also performs auto-versioning. Its aim and tools (like <a href="http://hudson-ci.org/" target="_blank">Hudson</a> etc.) should be known.</p><p></p><p><strong>15.ORM (Object relational mapping)</strong>: <a href="http://en.wikipedia.org/wiki/Object-relational_mapping" target="_blank">ORM</a> and its widely known implementation Hibernate framework is an important technique for mapping objects into database tables. It reduces code length and maintenance time.</p><p></p><p><strong>16.DI (Dependency Injection)</strong>: <a href="http://en.wikipedia.org/wiki/Dependency_injection" target="_blank">DI or IoC</a> (Inversion of Control) and its widely known implementation Spring framework makes life easy for object creation and lifetime management on big enterprise applications.</p><p></p><p><strong>17.Version controlling systems</strong>: <a href="http://en.wikipedia.org/wiki/Revision_control" target="_blank">VCS</a> tools (SVN, TFS, CVS etc.) are very important by saving so much time for collaborative works and versioning. Their logical viewpoint and standard cammands should be known. </p><p></p><p><strong>18.Internationalization (i18n)</strong>: <a href="http://en.wikipedia.org/wiki/Internationalization_and_localization" target="_blank">i18n</a> by extracting strings into external files is the best way of supporting multiple languages in our applications. Its practices on different IDEs and technologies must be known.</p><p></p><p><strong>19.Architectural patterns</strong>: Understanding <a href="http://www.codeproject.com/Articles/42830/Model-View-Controller-Model-View-Presenter-and-Mod" target="_blank">architectural design patterns</a> (like MVC, MVP, MVVM etc.) is essential for producing a maintainable, clean, extendable and testable source code.</p><p></p><p><strong>20.Writing clean code</strong>: Working code is not enough, it must be readable and maintainable also. So, <a href="http://en.wikipedia.org/wiki/Prettyprint" target="_blank">code formatting</a> and <a href="http://net.tutsplus.com/tutorials/html-css-techniques/top-15-best-practices-for-writing-super-readable-code/" target="_blank">readable code</a> development techniques are needed to be known and applied.</p></blockquote><p></p>
[QUOTE="Honda.putha, post: 28553655, member: 565644"] Here are the most important subjects for software engineering, with brief explanations: [B]1.Object oriented analysis & design[/B]: For better maintainability, reusability and faster development, the most well accepted approach, shortly [URL='http://en.wikipedia.org/wiki/Object-oriented_analysis_and_design']OOAD[/URL] and its [URL='http://en.wikipedia.org/wiki/SOLID_%28object-oriented_design%29']SOLID[/URL] principals are very important for software engineering. [B]2.Software quality factors[/B]: Software engineering depends on some very important [URL='http://en.wikipedia.org/wiki/Software_quality']quality factors[/URL]. Understanding and applying them is crucial. [B]3.Data structures & algorithms[/B]: Basic [URL='http://en.wikipedia.org/wiki/List_of_data_structures']data structures[/URL] like array, list, stack, tree, map, set etc. and useful [URL='http://en.wikipedia.org/wiki/List_of_algorithms']algorithms[/URL] are vital for software development. Their logical structure should be known. [B]4[/B]. [B]Big-O notation: [/B][URL='http://en.wikipedia.org/wiki/Big_O_notation']Big-O notation[/URL] indicates the performance of an algorithm/code section. Understanding it is very important for comparing performances. [B]5.UML notation[/B]: [URL='http://en.wikipedia.org/wiki/Unified_Modeling_Language']UML[/URL] is the universal and complete language for software design & analysis. If there is lack of UML in a development process, it feels there is no engineering. [B]6.Software processes and metrics[/B]: Software enginnering is not a random process. It requires a high level of systematic and some numbers to monitor those techniques. So, [URL='http://en.wikipedia.org/wiki/Software_development_process']processes [/URL]and [URL='http://en.wikipedia.org/wiki/Software_metric']metrics[/URL] are essential. [B]7.Design patterns[/B]: [URL='http://en.wikipedia.org/wiki/Software_design_pattern']Design patterns[/URL] are standard and most effective solutions for specific problems. If you don't want to reinvent the wheel, you should learn them. [B]8.Operating systems basics[/B]: Learning [URL='http://en.wikipedia.org/wiki/Operating_system']OS[/URL] basics is very important because all applications runs on it. By learning it, we can have better vision, viewpoints and performance for our applications. [B]9.Computer organization basics[/B]: All applications including OS requires a hardware for physical interaction. So, learning [URL='http://en.wikipedia.org/wiki/Microarchitecture']computer organization[/URL] basics is vital again for better vision, viewpoints and performance. [B]10.Network basics[/B]: [URL='http://en.wikipedia.org/wiki/Computer_network']Network[/URL] is related with computer organization, OS and the whole information transfer process. In any case we will face it while software development. So, it is important to learn network basics. [B]11.Requirement analysis[/B]: [URL='http://en.wikipedia.org/wiki/Requirements_analysis']Requirement analysis[/URL] is the starting point and one of the most important parts of software engineering. Performing it correctly and practically needs experience but it is very essential. [B]12.Software testing[/B]: [URL='http://en.wikipedia.org/wiki/Software_testing']Testing[/URL] is another important part of software engineering. [URL='http://en.wikipedia.org/wiki/Unit_testing']Unit testing[/URL], its [URL='http://richard.jp.leguen.ca/tutoring/soen343-f2010/tutorials/properties-of-good-unit-tests']best practices[/URL] and techniques like black box, white box, mocking, [URL='http://en.wikipedia.org/wiki/Test-driven_development']TDD[/URL], integration testing etc. are subjects which must be known. [B]13.Dependency management[/B]: Library (JAR, DLL etc.) management, and widely known tools (Maven, Ant, Ivy etc.) are essential for large projects. Otherwise, antipatterns like [URL='http://en.wikipedia.org/wiki/Java_Classloader#JAR_hell']Jar Hell[/URL] are inevitable. [B]14.Continuous integration[/B]: [URL='http://en.wikipedia.org/wiki/Continuous_integration']Continuous integration[/URL] brings easiness and automaticity for testing large modules, components and also performs auto-versioning. Its aim and tools (like [URL='http://hudson-ci.org/']Hudson[/URL] etc.) should be known. [B]15.ORM (Object relational mapping)[/B]: [URL='http://en.wikipedia.org/wiki/Object-relational_mapping']ORM[/URL] and its widely known implementation Hibernate framework is an important technique for mapping objects into database tables. It reduces code length and maintenance time. [B]16.DI (Dependency Injection)[/B]: [URL='http://en.wikipedia.org/wiki/Dependency_injection']DI or IoC[/URL] (Inversion of Control) and its widely known implementation Spring framework makes life easy for object creation and lifetime management on big enterprise applications. [B]17.Version controlling systems[/B]: [URL='http://en.wikipedia.org/wiki/Revision_control']VCS[/URL] tools (SVN, TFS, CVS etc.) are very important by saving so much time for collaborative works and versioning. Their logical viewpoint and standard cammands should be known. [B]18.Internationalization (i18n)[/B]: [URL='http://en.wikipedia.org/wiki/Internationalization_and_localization']i18n[/URL] by extracting strings into external files is the best way of supporting multiple languages in our applications. Its practices on different IDEs and technologies must be known. [B]19.Architectural patterns[/B]: Understanding [URL='http://www.codeproject.com/Articles/42830/Model-View-Controller-Model-View-Presenter-and-Mod']architectural design patterns[/URL] (like MVC, MVP, MVVM etc.) is essential for producing a maintainable, clean, extendable and testable source code. [B]20.Writing clean code[/B]: Working code is not enough, it must be readable and maintainable also. So, [URL='http://en.wikipedia.org/wiki/Prettyprint']code formatting[/URL] and [URL='http://net.tutsplus.com/tutorials/html-css-techniques/top-15-best-practices-for-writing-super-readable-code/']readable code[/URL] development techniques are needed to be known and applied. [/QUOTE]
Insert quotes…
Verification
Dawasata paya keeyak thibeda?
Post reply
Top
Bottom