{"id":433,"date":"2013-09-25T20:30:54","date_gmt":"2013-09-25T15:00:54","guid":{"rendered":"http:\/\/techliebe.com\/?p=433"},"modified":"2014-06-17T10:22:09","modified_gmt":"2014-06-17T04:52:09","slug":"communication-practices-in-software-engineering-1","status":"publish","type":"post","link":"https:\/\/techliebe.com\/communication-practices-in-software-engineering-1\/","title":{"rendered":"Communication Practices in Software Engineering-Part-1"},"content":{"rendered":"

Hi\u00a0 Guys, These are the basic principles of software engineering i am going to discuss with you.<\/p>\n

Requirement gathering activity<\/strong>: – Before customer requirement can be analyzed modeled or specified they must be gathering through commutation called Requirement gathering activity.<\/p>\n

Customer has a problem or requirement which is not compatible with computer based solution. A developer responds to customer\u2019s request for help which starts communications. Effective communication is most challenging activities for software engineer. So there is many principles apply equally to all of communication that occur within software project.<\/p>\n

 <\/p>\n

\"Communication<\/a><\/p>\n

 <\/p>\n

Some principles are following:-<\/b><\/p>\n

1) Listen carefully:<\/em><\/strong> –\u00a0\u00a0\u00a0 To understand customers requirement perfectly and listen carefully to speaker which ensure proper data collection. Ask for classification of something is under , but avoid constant interceptions. Concentrate on speakers\u2019 word so there should be any chance of misinterpretation.<\/p>\n

2) Prepare before you communicate<\/strong><\/em>: – spend the time to understand the problem before meeting with customer. If necessary, do some research to understand business terminologies .so it is necessary to prepare the agenda for meeting.<\/p>\n

3) Someone should facilitate the activity<\/strong><\/em>: – every communication meeting should have a leader to keep conversation moving in productive direction. To solve any conflict that does occur<\/p>\n

4) Face-to-face communication is best<\/strong><\/em>: – face-to-face communication is better but even if some document related to that particular subject or discuss is given. The drawing and documents speaks better.<\/p>\n

5) Take notes and document decision<\/em><\/strong>: – note down all important points and issue raised in the meeting maintain record. One participant of meeting may act as a recorder for the notes and document decision.<\/p>\n

6) <\/b>Strive for collaboration<\/em>:<\/strong> – collaboration in team members is essential for better team work. Collaboration is achieved when collective knowledge of member of the team is united to illustrate product of system function or system feature. It helps to build faith among team member and create generic goal for team. So the collaboration is very important in the team members.<\/p>\n

7) Stay focused, modularize your discussion<\/em> :-<\/b>\u00a0 the more people involved in any communication the more chances to bounce topic form one to other. The facilitator should keep conversation in one direction and important topic will be focused. so stay be focused modularize with your discussion.<\/p>\n

8) If something is unclear, draw a picture<\/em><\/strong> :- though verbal communication is important a sketch or drawing can be often provide clarity when words fails to do job so that\u2019s why draw the clear drawing or picture for particular stage.<\/p>\n

9) Keep the discussion to \u201c move on \u201d<\/strong> <\/em>:-<\/p>\n

a) once there is an agreement to do something.<\/p>\n

b) If you cannot agree to something.<\/p>\n

C) If a feature of function is not clear. In the meeting many people require to discussion different issues. So communication like any software engineering activity takes time .the people who participate should recognize many topics require discussion and that\u00a0 \u201c moving on \u201d is best option to achieve communication.<\/p>\n

10) Negotiation is successful when both parties win<\/strong><\/em> :- there are many instances in which software engineer and customer must negotiate function and feature priorities and delivery dates.<\/p>\n","protected":false},"excerpt":{"rendered":"

Hi  Guys, These are the basic principles of software engineering i am going to discuss with you. Requirement gathering activity: – Before customer requirement can be analyzed modeled or specified they must be gathering through commutation called Requirement gathering activity. Customer has a problem or requirement which is not compatible with computer based solution. A […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[13],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/techliebe.com\/wp-json\/wp\/v2\/posts\/433"}],"collection":[{"href":"https:\/\/techliebe.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/techliebe.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/techliebe.com\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/techliebe.com\/wp-json\/wp\/v2\/comments?post=433"}],"version-history":[{"count":5,"href":"https:\/\/techliebe.com\/wp-json\/wp\/v2\/posts\/433\/revisions"}],"predecessor-version":[{"id":916,"href":"https:\/\/techliebe.com\/wp-json\/wp\/v2\/posts\/433\/revisions\/916"}],"wp:attachment":[{"href":"https:\/\/techliebe.com\/wp-json\/wp\/v2\/media?parent=433"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/techliebe.com\/wp-json\/wp\/v2\/categories?post=433"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/techliebe.com\/wp-json\/wp\/v2\/tags?post=433"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}